[
https://issues.apache.org/jira/browse/BOOKKEEPER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440970#comment-13440970
]
Rakesh R commented on BOOKKEEPER-337:
-------------------------------------
Hi Sijie,
Its great and will help us to shape our thoughts on the following case. I hope
you were also thinking about handlingBookieFailure?
Also, could you please check my previous comment to get more on my view.
bq.I don't think the else part of this can ever be reached.
{code}
if (!metadata.currentEnsemble.get(bookieIndex).equals(addr)) {
} else {
handleBookieFailure(addr, bookieIndex);
}
{code}
Thanks,
Rakesh
> Add entry fails with MetadataVersionException when last ensemble has morethan
> one bookie failures
> -------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-337
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-337
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: Brahma Reddy Battula
> Assignee: Rakesh R
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-337.1.patch, BOOKKEEPER-337.diff,
> BOOKKEEPER-337-testtoreproduce.patch, BOOKKEEPER-337-try2.patch,
> BOOKKEEPER-337-try.patch
>
>
> Scenario:
> ========
> Start Five BK's
> Write ledger's with ensemble three and quroum size=2
> while write inprogress down two bookies(Bookies should be in ensemble)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
