[
https://issues.apache.org/jira/browse/BOOKKEEPER-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507378#comment-13507378
]
Ivan Kelly commented on BOOKKEEPER-485:
---------------------------------------
BookieHandleNotAvailableException is the closest to what has happened. The
channel has been closed, so the bookie handle, is in fact not available. If
clients need more details, they need to look at the logs. This isn't an error
they should be able to recover from. If this occurs they need to fix their code.
It's useful to know which thread triggered the connect. The log on connection
and disconnection are both INFO, so it made little sense to have this one as
DEBUG, and it was annoying to have to enable debug logging just for this output.
> TestFencing hung
> ----------------
>
> Key: BOOKKEEPER-485
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-485
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Flavio Junqueira
> Assignee: Ivan Kelly
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments:
> 0001-BOOKKEEPER-485-Fix-race-between-PerChannelBookieClie.patch,
> stack-trace-hung.txt
>
>
> ... while testing BOOKKEEPER-477, but I think they are unrelated.
--
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
