[
https://issues.apache.org/jira/browse/KAFKA-10812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871449#comment-17871449
]
Chris Egerton commented on KAFKA-10812:
---------------------------------------
Not seeing this anymore in our MM2 integration tests; marking resolved.
> Unclean worker shutdown in MirrorConnectorsIntegrationTest
> ----------------------------------------------------------
>
> Key: KAFKA-10812
> URL: https://issues.apache.org/jira/browse/KAFKA-10812
> Project: Kafka
> Issue Type: Bug
> Components: connect, mirrormaker
> Affects Versions: 2.7.0
> Reporter: Chris Egerton
> Priority: Major
>
> Although the flakiness for the {{MirrorConnectorsIntegrationTest}} has
> (hopefully) been addressed by https://github.com/apache/kafka/pull/9698, the
> root cause (unclean worker shutdown during those tests) has still not been
> addressed. This suggests that users of MirrorMaker 2 will see {{ERROR}}
> -level stack traces when shutting down workers running MM2
> (https://github.com/apache/kafka/blob/a57486e75084d70f1fbf22df9d3ffc3462302add/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/DistributedHerder.java#L301-L304),
> which looks fairly alarming, and may even indicate some problems with the
> functioning of MM2 itself.
> It'd be nice to diagnose the root cause of these unclean worker shutdowns
> when running MM2 during these tests and address them via improvements to the
> test cases, improvements to MM2 itself, or both.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
