[ https://issues.apache.org/jira/browse/BOOKKEEPER-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Merli resolved BOOKKEEPER-665. ------------------------------------- Resolution: Won't Fix The bookie reordering for reads proposed in BOOKKEEPER-772 is a better solution. > 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 > Components: bookkeeper-client > Reporter: Matteo Merli > Assignee: Matteo Merli > Priority: Minor > Fix For: 4.4.0 > > 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 was sent by Atlassian JIRA (v6.3.4#6332)