[
https://issues.apache.org/jira/browse/BOOKKEEPER-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sijie Guo resolved BOOKKEEPER-1061.
-----------------------------------
Resolution: Fixed
Issue resolved by merging pull request 149
[https://github.com/apache/bookkeeper/pull/149]
{noformat}
commit 5d43260e84c6121df72c0ee4c844651bfb726638
Author: Matteo Merli <mme...@apache.org>
AuthorDate: Mon May 15 12:35:26 2017 -0700
Commit: Sijie Guo <si...@apache.org>
CommitDate: Mon May 15 12:35:26 2017 -0700
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.
Author: Matteo Merli <mme...@apache.org>
Reviewers: Jia Zhai <None>, Sijie Guo <si...@apache.org>
Closes #149 from merlimat/bookie-watcher-thread
{noformat}
> 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)
