@kapa.ai ms sql destination throws this - "stacktrace" : "io.airbyte.workers.internal.exception.DestinationException: Destination process message delivery failed\n\tat io.airbyte.workers.general.BufferedReplicationWorker.writeToDestination(BufferedReplicationWorker.java:454)\n\tat io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsyncWithTimeout$5(BufferedReplicationWorker.java:244)\n\tat java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)\n\tat java.base/java.lang.Thread.run(Thread.java:1583)\nCaused by: java.io.IOException: Broken pipe\n\tat java.base/sun.nio.ch.UnixFileDispatcherImpl.write0(Native Method)\n\tat java.base/sun.nio.ch.UnixFileDispatcherImpl.write(UnixFileDispatcherImpl.java:65)\n\tat java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:137)\n\tat java.base/sun.nio.ch.IOUtil.write(IOUtil.java:102)\n\tat java.base/sun.nio.ch.IOUtil.write(IOUtil.java:72)\n\tat java.base/sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:300)\n\tat java.base/sun.nio.ch.ChannelOutputStream.writeFully(ChannelOutputStream.java:68)\n\tat java.base/sun.nio.ch.ChannelOutputStream.write(ChannelOutputStream.java:105)\n\tat java.base/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:309)\n\tat java.base/sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:381)\n\tat java.base/sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:357)\n\tat java.base/sun.nio.cs.StreamEncoder.lockedWrite(StreamEncoder.java:158)\n\tat java.base/sun.nio.cs.StreamEncoder.write(StreamEncoder.java:139)\n\tat java.base/java.io.OutputStreamWriter.write(OutputStreamWriter.java:219)\n\tat java.base/java.io.BufferedWriter.implFlushBuffer(BufferedWriter.java:178)\n\tat java.base/java.io.BufferedWriter.flushBuffer(BufferedWriter.java:163)\n\tat java.base/java.io.BufferedWriter.implWrite(BufferedWriter.java:334)\n\tat java.base/java.io.BufferedWriter.write(BufferedWriter.java:313)\n\tat java.base/java.io.Writer.write(Writer.java:278)\n\tat io.airbyte.workers.internal.VersionedAirbyteMessageBufferedWriter.write(VersionedAirbyteMessageBufferedWriter.java:39)\n\tat io.airbyte.workers.internal.LocalContainerAirbyteDestination.acceptWithNoTimeoutMonitor(LocalContainerAirbyteDestination.kt:137)\n\tat io.airbyte.workers.internal.LocalContainerAirbyteDestination.accept(LocalContainerAirbyteDestination.kt:96)\n\tat io.airbyte.workers.general.BufferedReplicationWorker.writeToDestination(BufferedReplicationWorker.java:439)\n\t... 5 more\n",

The error you're seeing —

DestinationException: Destination process message delivery failed

caused by

java.io.IOException: Broken pipe

— is a known issue in Airbyte that affects multiple destination connectors, including destination-mssql. [destination-mssql issue] What's Happening The

Broken pipe

error occurs when the destination connector process exits unexpectedly while the replication worker is still trying to write messages to it. The

BufferedReplicationWorker

attempts to write to the destination via

writeToDestination()

, but the underlying pipe to the destination container is already closed, resulting in the

IOException: Broken pipe

. [destination-mssql issue] This is a secondary/cascading error — the root cause is typically the destination process itself crashing or exiting with a non-zero exit code. The broken pipe is a symptom of that crash, not the primary cause. What to Look For To diagnose the actual root cause, you should look for: 1. The primary destination error — there is usually another failure entry in the logs with

failureOrigin: destination

that shows why the destination process actually crashed (e.g., a connector-specific error like a SQL error, schema mismatch, index creation failure, etc.). 2. Source-side errors — there may also be a

failureOrigin: source

entry indicating the source process was also affected. In the case of destination-mssql specifically, one known issue involves problems creating indexes for certain column types (e.g.,

_ab_cdc_*

columns from MongoDB sources). [destination-mssql issue] Recommended Steps 1. Check the full sync logs for additional failure entries — particularly any error logged before the broken pipe that shows why the destination process exited. 2. Check the destination connector version and ensure it is compatible with your platform version. 3. If the issue persists, consider filing a bug report on the Airbyte GitHub with your full logs, connector versions, and source/destination details. The knowledge sources do not contain enough information to pinpoint the exact root cause for your specific mssql scenario beyond what is described above. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.