Normalization pod failing to initialize

Connector Questions & Issues
,
1
  • Is this your first time deploying Airbyte?: No
  • Deployment: K8s via Helm
  • Airbyte Version: What version are you using now? 0.40.17
  • Source name/version: Postgres 1.0.22
  • Destination name/version: Postgres 0.3.26
  • Step: Process waits on Normalization pod to init, but it times out and errors before starting.

Log line prior to timeout:

Log4j2Appender says: Attempting to start pod = normalization-normalize-541-0-pelpm for airbyte/normalization:0.2.23 with resources io.airbyte.config.ResourceRequirements@fa284d9[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=]

When I kubectl get pods, the above normalization pod states:
State: Terminated
Reason: Error
Exit Code: 1

I am seeing this error in the Temporal pod:

{“level”:“error”,“ts”:“2022-11-07T13:44:22.795Z”,“msg”:“Internal service error”,“service”:“history”,“error”:“consistent query buffer is full, cannot accept new consistent queries”,“wf-id”:“connection_manager_c08fa6c4-d428-46a1-a43d-4534ef15bf0b”,“wf-namespace-id”:“74c3b8aa-5a76-4af8-a777-b378f19bf995”,“logging-call-at”:“handler.go:1788”,“stacktrace”:"go.temporal.io/server/common/log/loggerimpl.(*loggerImpl)

Not sure where I should go from here as far as investigating the normalization pods that get stuck initializing :shrug: I rolled back the Helm chart to 0.40.35 , but still erroring out.

2

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.
Best,
The Community Assistance Team

3

Hey Dusty,

Thanks for the question. Could you describe what your sync history is like? Are you performing many syncs at one time? How big are these syncs from Postgres to Postgres? When was normalization last working and with what version of AIrbyte?

Seems like an issue common to temporal: https://github.com/temporalio/temporal/issues/2749