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/05 17:08:02 UTC

[jira] [Resolved] (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:all-tabpanel ]

Uma Maheswara Rao G resolved BOOKKEEPER-419.
--------------------------------------------

    Resolution: Fixed

This issue already fixed along with HDFS-315
                
> 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: Uma Maheswara Rao G
>             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