I got the exception when search the dataset, so I guess I have to increase the timeout value or something to optimize the query ?

Caused by: java.util.concurrent.TimeoutException: Exceeded request timeout of 10000ms
	at com.linkedin.r2.transport.http.client.TimeoutTransportCallback$1.run(TimeoutTransportCallback.java:69)

which version of datahub are you running? where are you running datahub? Are you able to curl on elasticsearch and get a response?

datahub version: 0.8.16 I am running datahub in Google Compute engine with quickstart.sh yup, ES still response. I faced the problem with the dataset having very complex relationship. The remaining dataset are OK 😄

dataset having very complex relationship

can you elaborate on the relationships? This might be a case the team has not hit in their tests so far. So might not be optimized yet.

Is it possible that the relationship is self referencing, so that is causing an infinite loop?

@adamant-van-40260 Hi Hai! We'd love to understand the nature of your lineage graph to help us debug this issue!

I check my system, there are some duplicate urn ```https://datahub.mservice.io/dataset/urn:li:dataset:(urn:li:dataPlatform:ORACLE,UMARKET.soap_admin.gift,PROD)/Schema?is_lineage_mode=false``` ```https://datahub.mservice.io/dataset/urn:li:dataset:(urn:li:dataPlatform:ORACLE,UMARKET.SOAP_ADMIN.GIFT,PROD)/Schema?is_lineage_mode=false```