Source Process Exit Code 137 During TimescaleDB Sync

Summary

User reports an issue with Airbyte installation on Kubernetes where syncing data from TimescaleDB results in a source process exiting with non-zero exit code 137. Relevant logs indicate memory usage and exceptions during the replication process.


Question

hello all, i have a new installation of airbyte in my kube cluster and I am trying to ingest a timescaledb (postgres). Each time i try to sync, it seems to pull the data but then bails at the end with a “Source process exited with non-zero exit code 137”. Here seems to be the relevent logs

2024-01-12 16:05:50 destination > 2024-01-12 16:05:50 INFO i.a.c.i.d.b.BufferManager(printQueueInfo):118 - [ASYNC QUEUE INFO] Global: max: 4.69 GB, allocated: 190 MB (190.00144481658936 MB), % used: 0.03955726282980811 | Queue `timescaledbhigh_res`, num records: 693349, num bytes: 178.27 MB, allocated bytes: 180 MB | State Manager memory usage: Allocated: 10 MB, Used: 0 bytes, percentage Used 0.000000
2024-01-12 16:05:50 destination > 2024-01-12 16:05:50 INFO i.a.c.i.d.FlushWorkers(printWorkerInfo):146 - [ASYNC WORKER INFO] Pool queue size: 0, Active threads: 0
2024-01-12 16:06:20 replication-orchestrator > (pod: de91-bi / source-postgres-read-8-0-xisnv) - Closed all resources for pod
2024-01-12 16:06:20 replication-orchestrator > readFromSource: source exception
io.airbyte.workers.internal.exception.SourceException: Source process exited with non-zero exit code 137
        at io.airbyte.workers.general.BufferedReplicationWorker.readFromSource(BufferedReplicationWorker.java:365) ~[io.airbyte-airbyte-commons-worker-0.50.43.jar:?]
        at io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsyncWithHeartbeatCheck$3(BufferedReplicationWorker.java:235) ~[io.airbyte-airbyte-commons-worker-0.50.43.jar:?]
        at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
2024-01-12 16:06:20 replication-orchestrator > readFromSource: done. (source.isFinished:true, fromSource.isClosed:false)
2024-01-12 16:06:20 replication-orchestrator > processMessage: done. (fromSource.isDone:true, forDest.isClosed:false)
2024-01-12 16:06:20 replication-orchestrator > writeToDestination: done. (forDest.isDone:true, isDestRunning:true)
2024-01-12 16:06:20 replication-orchestrator > thread status... timeout thread: false , replication thread: true
2024-01-12 16:06:20 replication-orchestrator > Attempt 0 to update stream status incomplete public:high_res```


<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1705076882917659) if you want
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
['airbyte', 'kubernetes', 'timescaledb', 'source-exit-code-137', 'replication-orchestrator']
</sub>