[
https://issues.apache.org/jira/browse/ZOOKEEPER-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864306#comment-15864306
]
ASF GitHub Bot commented on ZOOKEEPER-2687:
-------------------------------------------
GitHub user arshadmohammad opened a pull request:
https://github.com/apache/zookeeper/pull/176
ZOOKEEPER-2687:Deadlock while shutting down the Leader server.
Leader server enters into deadlock while shutting down itself. Shutdown of
the leader server is called from the synchronized block which must be called
from outside the synchronized block. For detail pls refer ZOOKEEPER-2380
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arshadmohammad/zookeeper ZOOKEEPER-2687
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/176.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 #176
----
commit 1e3ed70b281e1afc9adc6a8c8ea72bef5b9c25e8
Author: Mohammad Arshad <ars...@apache.org>
Date: 2017-02-13T19:48:07Z
ZOOKEEPER-2687:Deadlock while shutting down the Leader server.
----
> Deadlock while shutting down the Leader server.
> -----------------------------------------------
>
> Key: ZOOKEEPER-2687
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2687
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.2, 3.6.0
> Reporter: Mohammad Arshad
> Assignee: Mohammad Arshad
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2687-01.patch
>
>
> Leader server enters into deadlock while shutting down. This happens some
> time only.
> The reason and deadlock flow is same as ZOOKEEPER-2380.
> shutdown was removed from synchronized block in ZOOKEEPER-2380
> Now shutdown is called from synchronized block from another place.
> {code}
> // check leader running status
> if (!this.isRunning()) {
> shutdown("Unexpected internal error");
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
