[
https://issues.apache.org/jira/browse/KAFKA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853186#comment-15853186
]
ASF GitHub Bot commented on KAFKA-4735:
---------------------------------------
GitHub user lindong28 opened a pull request:
https://github.com/apache/kafka/pull/2504
KAFKA-4735; Fix deadlock issue during MM shutdown
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lindong28/kafka KAFKA-4735
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2504.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2504
----
commit b0049582bf72a6cda8a8e46641f7dce640fab5a1
Author: Dong Lin <lindon...@gmail.com>
Date: 2017-02-05T10:18:55Z
KAFKA-4735; Fix deadlock issue during MM shutdown
----
> Fix deadlock issue during MM shutdown
> -------------------------------------
>
> Key: KAFKA-4735
> URL: https://issues.apache.org/jira/browse/KAFKA-4735
> Project: Kafka
> Issue Type: Bug
> Reporter: Dong Lin
> Assignee: Dong Lin
>
> In https://issues.apache.org/jira/browse/KAFKA-4521 we fixed a potential
> message reorder bug in MM. However, the patch introduced another bug that can
> cause deadlock during MM shutdown. The deadlock will happen if zookeeper
> listener thread call requestAndWaitForCommit() after MirrorMaker thread has
> already exited loop of consuming and producing messages.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
