Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hi everyone, I’m running a *self-hosted Airbyte deployment on Amazon Kubernetes (EKS) using Helm charts*, Airbyte version *1.8.5*. I’m seeing an issue where some syncs appear as *“Sync succeeded” in the UI*, but *no data gets loaded into the destination*.

:white_check_mark: What I’m seeing
Example run:
• *7 Jan 2026, 01:13*
• *19.09 MB*
• *9,792 records extracted*
• *0 records loaded*
*Job ID: 4067*
• Duration: *13m 20s*
From the logs, the *source connector successfully extracts records*, but the sync fails during the *destination write step* (we use *S3 as destination*).

:white_check_mark: Destination failure details
The replication summary shows the sync status as failed with 0 committed records:
```
"status" : "failed",
"recordsSynced" : 0,
"bytesSynced" : 0,
"recordsEmitted" : 9792,
"recordsCommitted" : 0```
And the failure is:
```
"failureOrigin": "destination",
"internalMessage": "Destination process exited with non-zero exit code 143",
"externalMessage": "Something went wrong within the destination connector"```
Log excerpt:
```
replication-orchestrator ERROR DestinationReader error:
replication-orchestrator ERROR DestinationWriter error:
Destination process exited with non-zero exit code 143```
:white_check_mark: Observations
The sync extracts data and begins destination processing (`part generation for data/...jsonl.gz` shows up)
But the destination container exits abruptly with *exit code 143*
No records are committed (`recordsCommitted = 0`, `bytesCommitted = 0`)
• In the Airbyte dashboard timeline, the sync entry still appears as *Sync succeeded*, even though replication summary status is failed
:question: What I need help with
1. *How should I debug exit code 143 for destination-s3 on Kubernetes?*
 (Is this likely SIGTERM due to OOMKill / eviction / timeout / resource constraints?)
2. *What logs / Kubernetes events should I inspect to confirm why destination is being terminated?*
3. Are there any known issues with *destination-s3 1.9.3* running under Airbyte *1.8.5*, especially on EKS?

Environment
Airbyte: *1.8.5*
Deployment: *Self-hosted on EKS*
Install: *Helm chart*
Destination: *S3 (destination-s3:1.9.3)*

Hi <@U08HWPLJBG8>, not sure if you have solved the issue, I am having something quite similar, instead my source connector exit with code 143.... wonder if you can give me any hint on it