Airbyte sync gets stuck if heartbeat stopped #39431
Replies: 1 comment
-
Airbyte AI (in slack) Suggested following solution which we tried and not working `To change file flags values like heartbeat.failSync on a Kubernetes OSS installation of Airbyte, you can configure these settings using the flags.yaml file. Here are the steps to do this:
Deploy the changes: After editing the flags.yaml file, you need to ensure that these changes are applied to your Kubernetes deployment. This typically involves updating the ConfigMap or Secret that contains the flags.yaml file and then restarting the relevant pods to pick up the new configuration.Here is a more detailed example of how you might update a ConfigMap in Kubernetes: apiVersion: v1 kubectl apply -f path/to/your/configmap.yaml kubectl rollout restart deployment |
Beta Was this translation helpful? Give feedback.
-
Airbyte sync is getting stuck for 3 hours if the heartbeat is stopped
Log says i.a.w.i.HeartbeatTimeoutChaperone(monitor):165 - Source has stopped heart beating
As per the docs https://github.com/airbytehq/airbyte/blob/ee24f8f5c9071baa5100c233c940d7db516094b8/docs/understanding-airbyte/heartbeats.md
We should set file flags heartbeat.failSync to true to make the syncs fail if a missed heartbeat is detected. But we are using OSS and file flags are not available in OSS.
Beta Was this translation helpful? Give feedback.
All reactions