Hello Team, I was facing the below issue in Lineage . when we click the Lineage tab for a dataset it take some time and pop up message “Failed to load results ! An unexpected error occurred” stay in same page with no data in the lineage. if we click the visualize Lineage then it shows the Lineage. Using the browser dev tools, I can see that a

searchAcrossLineage

GraphQL query was made and it is giving me 503 error. Also found the same issue reported few days back in the channel : https://datahubspace.slack.com/archives/C029A3M079U/p1673535713529589 We are currently on datahub v0.9.6.1

Hi @best-wire-59738, I think @echoing-airport-49548 can help you here!

Hi @best-wire-59738 what logs are you seeing in the GMS container?

Hello @echoing-airport-49548, Below are the logs that I found when navigating to lineage in GMS container. Apart from that I don’t have anything relevant on my side.

04:18:36.515 [ForkJoinPool.commonPool-worker-27] INFO  c.l.m.graph.neo4j.Neo4jGraphService:247 - MATCH (src {urn:"urn:li:dataset:(urn:li:dataPlatform:snowflake,gbi_sales_data_eng_db.sales_data_eng_app.accounts_pre_target,PROD)"})<-[r:Asserts ]-(dest )
04:18:36.516 [ForkJoinPool.commonPool-worker-23] WARN  org.elasticsearch.client.RestClient:65 - request [POST <http://elasticsearch-master:9200/dataset_operationaspect_v1/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true>] returned 2 warnings: [299 Elasticsearch-7.16.2-2b937c44140b6559905130a8650c64dbd0879cfb "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See <https://www.elastic.co/guide/en/elasticsearch/reference/7.16/security-minimal-setup.html> to enable security."],[299 Elasticsearch-7.16.2-2b937c44140b6559905130a8650c64dbd0879cfb "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."]
04:18:36.518 [ForkJoinPool.commonPool-worker-21] INFO  c.l.m.graph.neo4j.Neo4jGraphService:247 - MATCH (src {urn:"urn:li:dataset:(urn:li:dataPlatform:snowflake,gbi_sales_data_eng_db.sales_data_eng_app.accounts_pre_target,PROD)"})<-[r:Asserts ]-(dest )

It looks like you’re using Neo4j as your graph service?

yes, thats Right

Got it. Neo4j is less supported than Elastic for the DataHub Graph Service, but nonetheless you should be seeing some error logs

@echoing-airport-49548 No, I haven’t found any stack trace for 503