[
https://issues.apache.org/jira/browse/BOOKKEEPER-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005393#comment-16005393
]
ASF GitHub Bot commented on BOOKKEEPER-1061:
--------------------------------------------
GitHub user merlimat opened a pull request:
https://github.com/apache/bookkeeper/pull/149
BOOKKEEPER-1061: BookieWatcher should not do ZK blocking operations from ZK
async callback thread
In some cases, the BookieWatcher can get the ZK event thread stuck. This
happens when a ZK blocking request is issued from a ZK callback thread.
We should decouple the blocking requests in a separate executor to avoid
deadlocking ZK client.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/merlimat/bookkeeper bookie-watcher-thread
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/149.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 #149
----
commit a2f4b2956605020673725814574353fc3f88217a
Author: Matteo Merli <mme...@apache.org>
Date: 2016-09-27T00:12:01Z
BOOKKEEPER-1061: BookieWatcher should not do ZK blocking operations from ZK
async callback thread
----
> BookieWatcher should not do ZK blocking operations from ZK async callback
> thread
> --------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-1061
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1061
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Minor
> Fix For: 4.5.0
>
>
> In some cases, the BookieWatcher can get the ZK event thread stuck. This
> happens when a ZK blocking request is issued from a ZK callback thread.
> We should decouple the blocking requests in a separate executor to avoid
> deadlocking ZK client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
