Hello Team, I received notification 'Non-breaking ...
# replication-troubleshooting
z
Hello Team, I received notification 'Non-breaking schema updates detected' for my connection S3->Postgres, when I click review changes, I received error 'Failed to fetch schema. Please try again Error: non-json response'. And I'm not capable to change any settings about this connection without finishing review the schema update, so I'm kind of block. Any solutions/idea about this problem? Thx
a
Hi Zhaoxia-- thanks for sharing! I've flagged this issue with the team and we'll be taking a look. I'll follow-up when we have more details.
f
are you k8s with ingress?
👀 1
in k8s with ingress should configure timeout in LB to 300
a
Hi @Zhaoxia WANG, what version of Airbyte are you on?
z
@Anne Willborn (Airbyte) Hi, I'm using the https://cloud.airbyte.io/workspaces/xxx not sure the where indicate the version...😅
@Andy Jih (Airbyte) Thanks for your help Andy, I'm doing a POC for replacing Stitch by Airbyte, if this step blocks me, I couldn't move forward...🥲
m
I’m getting the same error. Also on k8s— 0.40.32
@Anne Willborn (Airbyte) this works locally, but fails in my k8s deployment
a
Hi there! The team published a fix to the S3 connector here so this issue should be fixed. You'll need to update your S3 connector to the latest version
0.1.32
. Can you give that a try and let us know if that resolves the issue?
m
image.png
I’m currently on that version
image.png
Same error
a
Ah gotcha-- I missed that there are some outstanding issues that the team is still working on: https://github.com/airbytehq/airbyte/pull/23189 https://github.com/airbytehq/airbyte/pull/23198 When those two get fixed and a new connector version is published, hopefully that will fix the issue.
m
To be clear, this works locally when testing in docker, but not k8s… Is that to be expected?
Those issues don’t really pertain to my use case 😕
a
Oh hm
That isn't expected
m
Looks like it was an nginx timeout, fixed
👍🏽 1
a
phew!
m
From the dev team:
I just disabled proxy buffering. It looked like the proxy buffer was overflowing onto the disk and I think airbyte wasn’t handling that transition very nicely. Figured rather than spend and eternity trying to figure out what the values for the buffer were needed we could just disable it for this ingress. We really do not need it for this application anyway and it seems happier with it off