[
https://issues.apache.org/jira/browse/BOOKKEEPER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-38:
---------------------------------
Attachment: BookieZKExpireTest.java
Patch looks good. However, you increase the standard timeout of the bookie from
10000 to 60000. Is this intentional?
I've attached a test case to ensure that this functionality works as proposed.
Could you integrate it with your patch.
Could you perhaps make the timeout into a constant or system property so that
the test can use it. I've used 10000 in my test as.
> Bookie Server doesn't exit when its zookeeper session is expired. So the
> process is hang there.
> -----------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-38
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-38
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 3.4.0
> Reporter: Sijie Guo
> Fix For: 3.4.0
>
> Attachments: BookieZKExpireTest.java, bookkeeper-38.patch
>
>
> Bookie server doesn't process zookeeper watcher events and just ignore them.
> So when session expires, bookie server hangs there and can't do nothing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
