[source-MongoDB] connector is getting BufferedReplicationWorker(readFromSource) exception

[AronsonDan]

Connector Name

source-mongodb

Connector Version

1.4.2

What step the error happened?

During the sync

Relevant information

Mongo source is constantly throwing errors on readFromSource

Relevant log output

2024-07-07 14:25:23 replication-orchestrator > readFromSource: source exception
io.airbyte.workers.internal.exception.SourceException: Source process exited with non-zero exit code 2
        at io.airbyte.workers.general.BufferedReplicationWorker.readFromSource(BufferedReplicationWorker.java:365) ~[io.airbyte-airbyte-commons-worker-0.50.38.jar:?]
        at io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsyncWithHeartbeatCheck$3(BufferedReplicationWorker.java:235) ~[io.airbyte-airbyte-commons-worker-0.50.38.jar:?]
        at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.lang.Thread.run(Thread.java:1583) ~[?:?]

### Contribute

- [ ] Yes, I want to contribute

[marcosmarxm]

@AronsonDan can you share the complete sync log file?

[AronsonDan]

@marcosmarxm Just added :-) 68c1d0e2_4cc2_43bc_b5db_99b9f5cea75d_job_71651_attempt_5_txt.txt

[AronsonDan]

@marcosmarxm We have been seeing the following behavior:

• The sync is running smoothly
• at a certain point of time it starts to show 101 records extracted
• looking at the logs of the sync, I can see silent error that dosent fail the sync

68c1d0e2_4cc2_43bc_b5db_99b9f5cea75d_job_71501_attempt_1_txt.txt

Attaching the log

[akashkulk]

Interesting. This seems to be an issue with debezium.

During shutdown, we are seeing that debezium shuts down correctly but still has a orphaned thread running which does not shut down correctly because it's waiting on some internal lock.

@AronsonDan can you try increasing the timeout here and trying again?

[AronsonDan]

@akashkulk How do I do that?