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

Posted to dev@bookkeeper.apache.org by "Uma Maheswara Rao G (JIRA)" <ji...@apache.org> on 2012/10/04 20:09:47 UTC

[jira] [Commented] (BOOKKEEPER-419) SingleFragmentCallback should be created with the fragment first entry id, not the first stored id

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

Uma Maheswara Rao G commented on BOOKKEEPER-419:
------------------------------------------------

ah, Just seen this issue here. Seems like I have taken care in BK-315 patch. Thanks for noticing it.
                
> SingleFragmentCallback should be created with the fragment first entry id, not the first stored id
> --------------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-419
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-419
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-auto-recovery
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.0
>
>
> The bad construction is in #replicateLedgerFragment. SingleFragmentCallback updates the metadata for that fragment, so it needs the first entry id to find the ensemble for that fragment.

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