You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2013/10/15 16:40:43 UTC
[jira] [Commented] (BOOKKEEPER-654) Bookkeeper client operations
are allowed even after its closure, bk#close()
[ https://issues.apache.org/jira/browse/BOOKKEEPER-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795238#comment-13795238 ]
Rakesh R commented on BOOKKEEPER-654:
-------------------------------------
I couldn't see another approach now, to handle the outstanding requests presents in PerChannelBookieClient when closing the client. In this case with my approach, client misses callback notification and would hangs forever. IMO, like [~ikelly] suggested, client should have a callback repository at the top layer.
> Bookkeeper client operations are allowed even after its closure, bk#close()
> ---------------------------------------------------------------------------
>
> Key: BOOKKEEPER-654
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-654
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.2.0
> Reporter: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 0001-BOOKKEEPER-654-Bookkeeper-client-operations-are-allo.patch, 0001-BOOKKEEPER-654-testcase-to-understand-more.patch, 0002-BOOKKEEPER-654.patch, 0003-BOOKKEEPER-654.patch, 0004-BOOKKEEPER-654.patch, 0005-BOOKKEEPER-654.patch, 0006-BOOKKEEPER-654-handled-inprogress-and-newrequests.patch
>
>
> User can perform below operations with the closed bookkeeper client, which was instantiated with external zkclient.
> - open a closed ledger
> - create a new ledger
> Also, ledgerhandle operations like fencing/add/write are infinitely hanging.
--
This message was sent by Atlassian JIRA
(v6.1#6144)