Hi Team, Currently i am facing slowness issue in d...
# troubleshoot
r
Hi Team, Currently i am facing slowness issue in datahub UI even in login process, it took about 7 seconds. It also happens in another process like table search, open glossary term very slow response in UI and sometimes it throwed an error in UI [Failed to load results! An unexpected error occurred]. However there is no error in datahub-gms log, only following message i found in the log when the error message shown in UI: WARN o.s.w.s.m.s.DefaultHandlerExceptionResolver:208 - Resolved [org.springframework.web.context.request.async.AsyncRequestTimeoutException] I tried in both version v.0.9.6.1 and v0.10.0. Here is the detail version and spec i use: • DataHub v0.10.0 • In total there are 3.9K Datasets, 43 Glossary terms. • docker compose file https://github.com/datahub-project/datahub/blob/v0.10.0/docker/quickstart/docker-compose-without-neo4j.quickstart.yml Memory info: free -m total used free shared buff/cache available Mem: 7780 7447 109 0 223 186 Swap: 20391 4458 15933 Could you please advise. Thanks in advance!
✅ 1
👀 1
i
Hello Hafidz, Deploying DataHub using docker compose is not recommended when you have a substantial amount of assets. In your case almost 4000. Most likely you need to scale elasticsearch.
You should move away from docker compose and consider a production grade deployment.
It could happen that your elastic is borked for some reason. Once the backup is completed you can try to delete the deployment with:
Copy code
datahub docker nuke
and then deploy a fresh local deployment with the backup you made before:
Copy code
datahub docker quickstart --version v0.10.0 --restore
r
Hi Pedro, thanks for the update. i'll backup the data first. Btw is there any specific config i can use to scale Elasticsearch?
i
No, quickstart is not designed to scale at runtime.
It is merely used for demo and local testing purposes
r
Hi Pedro, i did datahub docker nuke and deployed the fresh local deployment. i haven't restored the data however i am still facing slowness in login and the home page process. in order to have home page fully loaded it took 24 seconds without any data. i checked in the network browser there some long running graphql process . Could you please help on this.
i
Hello Hafidz, I am not familiar with the graphql queries that frontend performs. We are internally of an issue regarding duplicates calls being made. Don't know if that is your case or what the fix is. Today is a US holiday so I can not get any answers.
If you do some investigation on your end and create a GitHub issue for it, that would be great!