- Is this your first time deploying Airbyte?: No
- OS Version / Instance: Ubuntu
- Memory / Disk: 32 gb
- Deployment: docker
- Airbyte Version:
- Source name/version: n/a
- Destination name/version: n/a
- Step: During a sync
Hi all. Have been trying to do a post-mortem on a recent airbyte outage within our org.
Something happened one evening - not clear what - and this exception happened over and over for several days:
Caused by: io.temporal.failure.ApplicationFailure: message='Transitioning Job 888 from JobStatus FAILED to INCOMPLETE is not allowed. The only valid statuses that an be transitioned to from FAILED are [FAILED]', type='java.lang.IllegalStateException', nonRetryable=false
This was logged at INFO level over 14 million times over about 2 days - it went undetected.
After 2 days of the above, airbyte/temporal:0.40.18 was logging ERROR “consistent query buffer is full, cannot accept new consistent queries”. At this point our airbyte service was unresponsive. We trigger syncs through the airbyte API and later noticed that requests were timing out. Restarting the service resolved the issue.
Does anyone have any advice or ideas here? Is anyone able to clarify how the first exception may have happened, and what is it that would cause the “consistent query buffer full” issue? Looking to monitor/prevent this from occurring again.
Please let me know if any other info would help.
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
Hello paul-georgian, it’s been a while without an update from us. Are you still having problems or did you find a solution?
Apologies - had some vacation time and stepped away from this.
The issue was resolved upon restart of the containers, but we are still looking to learn more about what happened if possible. I’ll review the suggestions you left above and see if I can provide any more info to make it easier for people to respond.
I am facing this too in my K8S deployment
Hey @ramitheeb, are you still facing this issue? Could you share any details?