[
https://issues.apache.org/jira/browse/BOOKKEEPER-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490273#comment-13490273
]
Yixue (Andrew) Zhu commented on BOOKKEEPER-365:
-----------------------------------------------
In general, Quorum based read/write requires that Qw + Qr > Q. e.g. the
ensemble size is 3, write quorum is 2, read quorum needs to be at least 2.
In BK, we relax it by using read quorum 1. It works because it never updates an
entry once its written.
In your example, it seems the ensemble size 3, read quorum 1, write quorum 2.
During recovery, we can raise the standard, requiring read quorum 2, which
address above issue.
> Ledger will never recover if one of the quorum bookie is down forever and
> others dont have entry
> ------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-365
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-365
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Sijie Guo
> Fix For: 4.2.0
>
>
> As discussed in BOOKKEEPER-355, current fix to handle the below issue is not
> correct. Need to find out new solution
> If some bookies of a quorum gone forever, some bookies of this quorum are
> still alive but doesn't have that entry (NoSuchEntry or NoSuchLedger), then
> the ledger doesn't have any evidence to recovery/close it.
--
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
