You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2012/12/14 11:06:12 UTC

[jira] [Created] (BOOKKEEPER-510) LedgerRecoveryOp updates metadata before it needs to

Ivan Kelly created BOOKKEEPER-510:
-------------------------------------

             Summary: LedgerRecoveryOp updates metadata before it needs to
                 Key: BOOKKEEPER-510
                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-510
             Project: Bookkeeper
          Issue Type: Bug
            Reporter: Ivan Kelly
             Fix For: 4.3.0


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 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