[BOOKKEEPER-667] Client write will fail with BadMetadataVersion in case of multiple Bookie failures with AutoRecovery enabled

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.2.1
• Fix Version/s: 4.2.2, 4.3.0
• Component/s: bookkeeper-auto-recovery
• Assignee: Sijie Guo
• Reporter: Vinayakumar B
• Created: 06/Aug/13 06:29
• Updated: 13/Aug/13 13:11
• Resolved: 13/Aug/13 13:02

Description

Scenario:
------------
1. Start cluster of enough bookies, say 4, with autorecovery
2. Create ledger and write some entries.
3. Restart one of the bookies
4. again, write some more entries
5. wait for some time.. till autorecovery completes replication of first segment
6. Now restart one of the bookie of latest ensemble
7. continue to write.

Here second ensemble change will fail, throwing BadMetadataVersion

Issue Links

• relates to: BOOKKEEPER-112 Bookie Recovery on an open ledger will cause LedgerHandle#close on that ledger to fail