@kapa.ai I observed a pattern whenever logs count reach 1000000 rows in airbyte, the sync fails with

Warning from source: Something went wrong within the source connector

More details
Source process exited with non-zero exit code 143

Is this a known issue ?

Yes, this is a known and recurring issue in Airbyte. Exit code 143 typically indicates that the source process was killed by the operating system, most commonly due to an Out of Memory (OOM) condition when processing large volumes of data. Several community reports and GitHub issues confirm this pattern: • A Mixpanel sync failing with exit code 143 (OOM) after processing ~1.7M rows (~500MB) is documented as a known memory handling issue. [Mixpanel OOM Issue] • A customized source connector failing with exit code 143 when syncing ~584 MB of data on Kubernetes was reported, with the suggested fix being to increase

JOB_MAIN_CONTAINER_MEMORY_REQUEST

. [Forum: Exit Code 143] • A CockroachDB connector consuming ~49.7 GB of RAM for an 18 GB table before throwing OOM is another example of memory pressure at large row counts. [CockroachDB Failures] • A sync worker cancellation log explicitly states: "Source process exit with code 143. This warning is normal if the job was cancelled." — though in your case it appears to be OOM-triggered rather than a manual cancellation. [Sync Cancellation] Recommended Mitigations 1. Increase memory allocation for sync jobs by raising these environment variables (for self-hosted deployments): ◦

JOB_MAIN_CONTAINER_MEMORY_REQUEST

(e.g., to

4Gi

or

8Gi

) ◦

JOB_MAIN_CONTAINER_MEMORY_LIMIT

1. Reduce the sync scope — if possible, sync smaller date ranges or subsets of data to reduce memory pressure at any one time. [Mixpanel OOM Issue] 2. Upgrade Airbyte and connector versions — some memory improvements have been made in newer versions. [Forum: Large Sync Fails] 3. Check for memory leaks in the specific connector — some connectors have been found to use significantly more memory than the raw data size would suggest. [CockroachDB Failures] If you're on Airbyte OSS/self-hosted, the most immediate fix is to increase the memory limits for your sync containers. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.