[
https://issues.apache.org/jira/browse/BOOKKEEPER-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729641#comment-13729641
]
Matteo Merli commented on BOOKKEEPER-665:
-----------------------------------------
If zk service totally down, only an application that just uses a single (or a
few) ledger to read/write could possibly keep on working. I believe that in
most of the cases applications are constantly opening/creating ledgers, in
which case being able to operate without ZK will be of little help.
If a bookie is partition from the network and it's the 1st one in the ensemble
list, then every read to all the ledgers it contains will timeout in 2s, even
if we have perfectly fine copies of that. Also, trying to read from dead
bookies is especially annoying when doing automatic replication, because it
tries to read every fragment from the failed bookie, filling the logs with
1000s of errors.
> 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
