Hello! During replication in Airbyte I am periodically encountering the following errors: • Workload Heartbeat Error • Workload failed, source: workload-monitor-heartbeat •

Failed to connect to airbyte-workload-api-server-svc:8007 (Connection refused)

•

No exit code found. exitCode.txt does not exist

In the logs it looks like the sync crashes in the middle of the process, and the source container does not manage to write the

exitCode.txt

file before termination. The data size per sync is approximately: • 3.7M records emitted (~379 MB total) • 3 streams (around 1M, 1.58M and 1.126M records) • The sync runs for ~4 minutes before failing. ❓ Questions for Support Could you please help me understand the root cause and how to resolve this issue? 1. What could cause the Workload Heartbeat Error? 2. Specifically, why would the workload be unable to connect to

airbyte-workload-api-server-svc:8007

(Connection refused)? 3. Why does the workload container fail to create

exitCode.txt

? 4. This seems to indicate the container crashes abruptly rather than exiting gracefully. 5. Could this problem be related to insufficient resources (RAM/CPU) on the workload container or the workload-api-server? 6. If so, what are the recommended resource requirements for handling large syncs (~4M records / ~400 MB)? 7. Are there any known issues in Airbyte where the Workload API Server loses connection during high-volume syncs? 8. What additional logs or metrics would you need from my environment to further diagnose the issue? 9. (pods logs, describe output, node metrics, etc.) 10. Do you have recommended approaches for optimizing large syncs? 11. For example: ◦ Increasing workload / heartbeat timeouts ◦ Tuning CPU/RAM for workloads or API server ◦ Splitting the sync into smaller batches ◦ Using the new Worker mode or other scaling strategies