[
https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658021#comment-15658021
]
ASF GitHub Bot commented on KAFKA-4399:
---------------------------------------
GitHub user resetius opened a pull request:
https://github.com/apache/kafka/pull/2125
KAFKA-4399; deadlock cleanupGroupMetadata and offset commit fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/resetius/kafka KAFKA-4399
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2125.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 #2125
----
commit e7e6c4fcff0cb72f6dac46a3c6416ee128e6028c
Author: Alexey Ozeritsky <aozerit...@yandex-team.ru>
Date: 2016-11-11T19:58:31Z
KAFKA-4399; deadlock cleanupGroupMetadata and offset commit fixed
----
> Deadlock between cleanupGroupMetadata and offset commit
> -------------------------------------------------------
>
> Key: KAFKA-4399
> URL: https://issues.apache.org/jira/browse/KAFKA-4399
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.1.0
> Reporter: Alexey Ozeritskiy
> Priority: Blocker
> Attachments: deadlock-stack
>
>
> We have upgraded our clusters to 0.10.1.0 and got deadlock issue.
> We thought it smth like https://issues.apache.org/jira/browse/KAFKA-3994, but
> patch did not help us and our stacks is different. I think it is other issue.
> Stack traces attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
