[
https://issues.apache.org/jira/browse/BOOKKEEPER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925407#comment-13925407
]
Sijie Guo commented on BOOKKEEPER-510:
--------------------------------------
moved it out of 4.3.0, which seems not to be an issue. [~ikelly] if you could
clarify the really issue and want to include it in 4.3.0, please feel free to
add it back.
> LedgerRecoveryOp updates metadata before it needs to
> ----------------------------------------------------
>
> Key: BOOKKEEPER-510
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-510
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Reporter: Ivan Kelly
> Attachments:
> 0002-BOOKKEEPER-510-LedgerRecoveryOp-updates-metadata-bef.patch
>
>
> This could lead to an issue if there are a lot of errors in a specific order.
> You have a ledger with ensemble (B1, B2, B3)
> # B1 brought down for maintenance
> # Ledger recovery started
> # B2 answers read last confirmed.
> # B1 replaced in ensemble by B4
> # Write to B4 fails for some reason
> # B1 comes back up.
> # B2 goes down for maintenance.
> # Ledger recovery starts (ledger is now unavailable)
> See BOOKKEEPER-355
--
This message was sent by Atlassian JIRA
(v6.2#6252)
