Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All connectors after upgrading to version 1.4.0 are taking atleast 15 minutes to sync #53180

Closed
Swadish opened this issue Feb 5, 2025 · 2 comments

Comments

@Swadish
Copy link
Contributor

Swadish commented Feb 5, 2025

Helm Chart Version

1.4.0

What step the error happened?

During the Sync. After upgrading from 1.2.0 to 1.4.0.

Relevant information

All connectors on version 1.4.0 are taking atleast 15 minutes to sync.
Previously, many of them synced in less than two minutes:

Image

Image

Relevant log output

2025-02-05 01:02:54 platform INFO Closing Segment analytics client...
2025-02-05 01:02:54 platform INFO Waiting for Segment analytic client to flush enqueued messages...
2025-02-05 01:02:54 platform INFO Segment analytic client flush complete.
2025-02-05 01:02:54 platform INFO Segment analytics client closed.  No new events will be accepted.
2025-02-05 01:15:16 platform INFO 
----- START POST REPLICATION OPERATIONS -----

2025-02-05 01:15:16 platform INFO No post-replication operation(s) to perform.
2025-02-05 01:15:16 platform INFO 
----- END POST REPLICATION OPERATIONS -----
@LucasSegersFabro
Copy link

LucasSegersFabro commented Feb 5, 2025

It seems to be an issue with the helm chart
the workload-server-api wasn't being deployed with this error:

failed to replace object: Deployment.apps "airbyte-workload-api-server" is invalid: [spec.template.spec.containers[0].volumeMounts[1].name: Not found: "db", spec.template.spec.containers[0].volumeMounts[1].mountPath: Required value]

All of the other deployments got updated as expected, but this one was running and old version

After manually upgrading the deployment to the 1.4.0 tag it got back to work

Good news is: it seems to auto-heal after 15 minutes like the release said it would :P

@Swadish
Copy link
Contributor Author

Swadish commented Feb 5, 2025

(@LucasSegersFabro is from my company) that was the soluction.

@Swadish Swadish closed this as completed Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants