[
https://issues.apache.org/jira/browse/BOOKKEEPER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sijie Guo updated BOOKKEEPER-337:
---------------------------------
Attachment: BOOKKEEPER-337-try.patch
yup, ur right. the confliction occurred due to there are more than two
changing-same-ensemble requests sending on-the-fly. but
LedgerMetadata#resolveConflict doesn't handle this case. so it threw the
MetadataVersionException.
I think the simple fix would be improve LedgerMetadata#resolveConflict to
handle this case. I attached a draft about it and also add some logging
messages to inform users that there are more than two changing-same-ensemble
requests are processing.
but I don't think the fix is best. since it introduced overhead to maintain
confliction cases that we need to handle in LedgerMetadata#resolveConflict. for
long term plan, seems that we need to find better solution to resolve
confliction.
> 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
> Reporter: Brahma Reddy Battula
> Assignee: Rakesh R
> Attachments: 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
