MSK Connect issue following upgrade to 3.3.1.Final & Kafka 3.9
15 views
Skip to first unread message
Joe Eckert
Dec 14, 2025, 1:03:17 PM (9 days ago) Dec 14
to debezium
It seems that the behavior of the MSK connect during a cluster security patch causes a Debezium restart. We're seeing a zombie active pid on the slot preventing the restarted debezium process from ingesting logs. Terminating the backend zombie pid does not kill the old process. Only way we've been able to mitigate is deleting the MSK connector and redeploying. Curious if anyone has a fix for this.
Much appreciated!
Reply all
Reply to author
Forward
0 new messages