[ https://issues.apache.org/jira/browse/BOOKKEEPER-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871815#comment-13871815 ]
Sijie Guo commented on BOOKKEEPER-510: -------------------------------------- [~ikelly] I still don't understand. This issue seems not be a problem anymore. - recovery only updates metadata when close since BOOKKEEPER-355 - recovery op keeps a copy of metadata for recovery reading in BOOKKEEPER-510. Could you clarify what is the ticket for? if not an issue, shall we close it? > 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 > Fix For: 4.3.0 > > 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.1.5#6160)