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

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2014/03/12 18:13:43 UTC

[jira] [Commented] (BOOKKEEPER-710) OpenLedgerNoRecovery should watch ensemble change.

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

Sijie Guo commented on BOOKKEEPER-710:
--------------------------------------

[~ikelly] I marked this for 4.2.3 when I created the ticket. this is a bug fix not a new feature. we should get it in 4.2.3. but I have no idea why it is on reopened state.

> OpenLedgerNoRecovery should watch ensemble change.
> --------------------------------------------------
>
>                 Key: BOOKKEEPER-710
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-710
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-client
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>            Priority: Blocker
>             Fix For: 4.3.0, 4.2.3
>
>         Attachments: BOOKKEEPER-710.diff
>
>
> LedgerHandle opened by openLedgerNoRecovery should watch ensemble change. otherwise, readLastConfirmed & readEntries will stuck if there are ensemble changes in the ledger.



--
This message was sent by Atlassian JIRA
(v6.2#6252)