getting the following error in the UI trying to vi...
# troubleshoot
h
getting the following error in the UI trying to view lineage for snowflake lineage
Copy code
Failed to load results! An unexpected error occurred.
the graph lineage works and lineage works for my looker objects, any ideas? I think im just going to restart the pods and see if that helps but any ideas appreciated
1
a
What version are you on, and did the snowflake ingestion occur without error?
a console stacktrace from browser would be helpful as well
h
we're on 9.6 right now - yes the snowflake ingestion is happening correctly. gms logs don't show anything but we are seeing a graphql call getting a 503 when trying to look at the lineage.
the behavior we are seeing is identical to the issues reported in these threads from a few months ago - do you know if and how these were resolved?: https://datahubspace.slack.com/archives/C029A3M079U/p1673560800455289?thread_ts=1673535713.529589&cid=C029A3M079U https://datahubspace.slack.com/archives/C029A3M079U/p1671652168427829
tagging my colleague @aloof-branch-47277 on this thread for his visibility as well
a
Are you using neo4j as your graph backend? What is your deployment env?
0.9.6 had a secrets bug that was patched, which made it unable to use secrets from older deploys, and secrets created in it invalid in other versions. If you’ve recently upgraded, this could be the secrets failing
h
@aloof-branch-47277 correct me if i'm wrong but i believe we're using elasticsearch on aws
a
Yup that's correct ^ we're using elasticsearch on AWS as our graph backend, our deployment env is eks installed with the helm charts also using datahub's kafka setup within EKS and then postgres (AWS RDS) as our DB
a
Did you try the update away from base 0.9.6?
h
we did but the update failed right @aloof-branch-47277
and now we don't have it at all
a
Hi, are y’all still experiencing this issue? It might be more fruitful to troubleshoot the upgrade
h
we figured it out! it was actual just timing out so we increased the timeout on the api gateway we had set up. thanks for following up!!