Airbyte UI stops responding without error

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu 20.45 GCP VM Instance
  • Memory / Disk: e2-standard-16 16 CPUs, 64 GB Ram
  • Deployment: Docker
  • Airbyte Version: 0.41.0
  • Source name/version: Postgres 1.0.51
  • Destination name/version: Bigquery 1.2.14
  • Step: Stops working without any error, no specific trigger
  • Description:
    We upgraded the version from 0.40.32 to 0.41.0 recently. The upgrade went as expected and data was being replicated. After a couple of days the UI suddenly stopped responding, with just the airbyte logo loading.
    This keeps happening until we either restart the VM or ssh into the VM and restart airbyte-temporal container. This has reoccured multiple times since the upgrade. No other change to the schema configuration was done.

When we check the docker logs for airbyte-temporal this error shows up at a very high rate -

{“level”:“info”,“ts”:“2023-03-29T04:23:10.179Z”,“msg”:“query directly through matching on sticky timed out, attempting to query on non-sticky”,“service”:“history”,“shard-id”:3,“address”:“”,“shard-item”:“0xc0005fe380”,“component”:“history-engine”,“wf-namespace”:“default”,“wf-id”:“connection_manager_780d30bf-e538-4ad4-867a-ded789e2db56”,“wf-run-id”:“d13be803-5930-4576-aaa2-c3650edc5340”,“wf-query-type”:“getState”,“wf-task-queue-name”:“”,“wf-next-event-id”:36,“logging-call-at”:“historyEngine.go:923"}

Any advice on how this can be fixed?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team