Logging for custom connectors broken after upgrade - hanging/not logging after "Starting a new buffer for stream" #28830
Unanswered
luke-oa
asked this question in
Connector Questions
Replies: 2 comments
-
I also just confirmed that the extra logs aren't being written to S3, so the issue appears to be with writing, not reading via the API |
Beta Was this translation helpful? Give feedback.
0 replies
-
Did confirm I can see the full source logging output if I |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We're recently upgraded our Airbyte deployment (via Kubernetes and Helm) from
0.40.29
to0.50.6
. After upgrade, I've noticed that our custom connectors stop logging if we start a new stream buffer. The pods still run in the background, and if left alone they still finish after awhile; however, after starting the new buffer, the source never logs again, and the normalization logs incorrectly (formatting is off - no green highlighting).This appears to have come up in discussion (without resolution) here and as a GH issue (without resolution except the classic "upgrade" motto) here.
Here's an example log (note the jump from 20:45 to 04:06 - nearly 8 hours where things should have been logging but nothing came through):
Beta Was this translation helpful? Give feedback.
All reactions