You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2012/05/02 00:20:52 UTC
[jira] [Commented] (BOOKKEEPER-225) Handle session expires and
disconnect events in BookKeeper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266192#comment-13266192 ]
Flavio Junqueira commented on BOOKKEEPER-225:
---------------------------------------------
Hi Uma, Just a few things to keep in mind. If a client loses its zookeeper session, then it is not able to update the metadata of the ledgers it currently has open. Not being able to update the metadata of ledgers means that the client can't close ledgers or change the ensemble of ledgers it is writing to.
Upon a session expiration, there are two options I see:
# to ignore until an operation to update the metadata fails because the zookeeper handle is broken. I don't see a reason for violating correctness if we do it.
# to fail any attempt to execute an operation. This is a conservative approach, but also seems to be fine.
I was also thinking about the approach to take for the bookkeeper object. Should we try to replace the zookeeper handle or fail any operation on the bookkeeper client once the session expires? With the second option we are essentially telling the application to create a new bookkeeper object. It might also be complicated to replace the zk handle because we have a bookkeeper constructor that takes one, so it is not a desirable behavior to replace the zk handle.
> Handle session expires and disconnect events in BookKeeper
> -----------------------------------------------------------
>
> Key: BOOKKEEPER-225
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-225
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
>
> Currently BookKeeper is not handling session disconnects and expires events. We have to handle them for continueing from clients.
--
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