[
https://issues.apache.org/jira/browse/BOOKKEEPER-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715462#comment-13715462
]
Sijie Guo commented on BOOKKEEPER-654:
--------------------------------------
We should find why the operations are hanging and fix them, rather than just
adding checking. As my knowledge, all the following bookie request should fail
if bookie client is closed since it would mark bookie client as closed, so no
connection would be established again and all existing channel also are closed
and supposed to fail requests. (check following code)
{code}
public void close() {
closeLock.writeLock().lock();
try {
closed = true;
for (PerChannelBookieClient channel: channels.values()) {
channel.close();
}
} finally {
closeLock.writeLock().unlock();
}
}
{code}
> 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
