Error with mongo connector 1.5.9 - Java heap space

Summary

The user is facing an error with the mongo connector 1.5.9 due to Java heap space, resulting in a SourceException with a non-zero exit code.


Question

Hello, anyone knows how solve this error, is the mongo connector 1.5.9 Terminating due to java.lang.OutOfMemoryError: Java heap space
2024-09-02 17:42:25 platform > readFromSource: source exception
io.airbyte.workers.internal.exception.SourceException: Source process exited with non-zero exit code 3
at io.airbyte.workers.general.BufferedReplicationWorker.readFromSource(BufferedReplicationWorker.java:366) ~[io.airbyte-airbyte-commons-worker-0.50.46.jar:?]
at io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsyncWithHeartbeatCheck$3(BufferedReplicationWorker.java:235) ~[io.airbyte-airbyte-commons-worker-0.50.46.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) [?:?]



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["mongo-connector", "java-heap-space", "source-exception", "airbyte-platform"]

Terminating due to java.lang.OutOfMemoryError
Have you tried to set more memory to container/pod?

<@U05JENRCF7C> yes, i have a vm in gcp with 16G of ram and i have this in the .env file

abctl / docker compose / helm charts deployment?

it’s a docker compose deployment

I’d use ctop https://github.com/bcicen/ctop to check how many resources other containers consume. Probably the easiest option would be to increase memory for VM.

Thanks <@U05JENRCF7C> , i have migrate to abctl and now i have a issue with big query conection