You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Vinay (JIRA)" <ji...@apache.org> on 2013/08/06 08:34:52 UTC
[jira] [Updated] (BOOKKEEPER-667) Client write will fail with
BadMetadataVersion in case of multiple Bookie failures with AutoRecovery
enabled
[ https://issues.apache.org/jira/browse/BOOKKEEPER-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinay updated BOOKKEEPER-667:
-----------------------------
Component/s: bookkeeper-auto-recovery
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
Affects Version/s: 4.3.0
4.2.1
Summary: Client write will fail with BadMetadataVersion in case of multiple Bookie failures with AutoRecovery enabled (was: Client write will get )
> Client write will fail with BadMetadataVersion in case of multiple Bookie failures with AutoRecovery enabled
> ------------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-667
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-667
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-auto-recovery
> Affects Versions: 4.2.1, 4.3.0
> Reporter: Vinay
>
> 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
--
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