You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2012/06/01 11:58:23 UTC
[jira] [Comment Edited] (BOOKKEEPER-279) LocalBookKeeper is failing
intermittently due to zkclient connection establishment delay
[ https://issues.apache.org/jira/browse/BOOKKEEPER-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287305#comment-13287305 ]
Sijie Guo edited comment on BOOKKEEPER-279 at 6/1/12 9:57 AM:
--------------------------------------------------------------
[~rakeshr] the patch introduced junit package in LocalBookKeeper. but junit package scope is just for testing. It would be better to remove junit-related staffs from LocalBookKeeper.
was (Author: hustlmsp):
[~rakeshr] the patch introduced junit package in LocalBookKeeper. but junit package scope is just for testing. I would be better to remove junit-related staffs from LocalBookKeeper.
> LocalBookKeeper is failing intermittently due to zkclient connection establishment delay
> ----------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-279
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-279
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.0.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.1.0
>
> Attachments: BOOKKEEPER-279.1.patch, BOOKKEEPER-279.patch
>
>
> LocalBookKeeper is initializing the zkclient and immediately trying to create "/ledgers" and "/ledgers/available" znodes without waiting for the ZooKeeper SyncConnected state. The client operation should be guarded with ZKConnectionWatcher.
> LocalBookKeeper.java
> {noformat}
> zkc = new ZooKeeper("127.0.0.1", ZooKeeperDefaultPort, new emptyWatcher());
> /* User for testing purposes, void */
> static class emptyWatcher implements Watcher {
> public void process(WatchedEvent event) {}
> }
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira