[
https://issues.apache.org/jira/browse/BOOKKEEPER-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716056#comment-13716056
]
Sijie Guo commented on BOOKKEEPER-654:
--------------------------------------
{code}
@Override
public final void operationComplete(final int rc, final T result) {
executor.submitOrdered(orderingKey, new SafeRunnable() {
@Override
public void safeRun() {
safeOperationComplete(rc, result);
}
});
}
{code}
looks like you find the root cause, you should catch the exception and fix the
callback directly in OrderedSafeGenericCallback.
the only concern is that we should put such checking in a central place rather
then spreading it over through the code base.
> 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
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 0001-BOOKKEEPER-654-testcase-to-understand-more.patch,
> 0002-BOOKKEEPER-654.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
