[jira] [Commented] (BOOKKEEPER-665) BK client should not try to read entries from non-available bookies

["Sijie Guo (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728984#comment-13728984 ] 

Sijie Guo commented on BOOKKEEPER-665:
--------------------------------------

-1 for the solution ignoring the bookie not in zk, since it is against the goal in BOOKKEEPER-537 (we could still read/write entries even zookeeper is totally down). 
                
> BK client should not try to read entries from non-available bookies
> -------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-665
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-665
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Matteo Merli
>            Assignee: Matteo Merli
>            Priority: Minor
>         Attachments: BOOKKEEPER-665.patch
>
>
> If a bookie is not in the available list, we shouldn't try to read from it but just treat the read from that replica as failed.
> This could be especially true if the bookie node is partitioned because that could mean we need to wait the connection timeout. Also during the auto-replication of ledgers most of the logs consist of errors that say it was not possible to read from the failed bookie.

--
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