[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612906#comment-13612906
 ] 

Hudson commented on BOOKKEEPER-581:
-----------------------------------

Integrated in bookkeeper-trunk #154 (See 
[https://builds.apache.org/job/bookkeeper-trunk/154/])
    BOOKKEEPER-581: Ledger recovery doesn't work correctly when recovery adds 
force changing ensembles. (sijie via ivank) (Revision 1460765)

     Result = SUCCESS
ivank : 
Files : 
* /zookeeper/bookkeeper/trunk/CHANGES.txt
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerMetadata.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerRecoveryOp.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingReadOp.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/LedgerRecoveryTest.java

                
> Ledger recovery doesn't work correctly when recovery adds force changing 
> ensembles.
> -----------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-581
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-581
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-client
>    Affects Versions: 4.2.0, 4.2.1
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>            Priority: Critical
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-581.patch
>
>
> currently read and write use same ledger metadata during ledger recovery, 
> which is bad. since write will cause changing ensemble which modified 
> ensembles map to introducing brand new bookies. those brand new bookies would 
> mislead following recovery reads, cause recovery is proceeded in a wrong way.
> E.g.
> 3 bookies, quorums size 2. A, B, C.
> read 0 from A, B.
> recovery add 0: A, B becomes slow. D, E are brought into the ensemble to 
> replace A, B.
> so following recovery read would be proceed in ensemble (D, E, C), then we 
> would lost all the entries added in A and B.
> this issue is similar as 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

Reply via email to