You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2012/07/04 12:23:34 UTC

[jira] [Updated] (BOOKKEEPER-246) Recording of underreplication of ledger entries

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-246:
----------------------------------

    Attachment: BOOKKEEPER-246.diff

Addressed Rakesh's comments. I didn't add a factory interface, because it's not necessary yet. We don't know if there will be different implementations of LedgerUnderreplicationManager. Having the interface makes it easy to add one later, but adding a factory doesn't give us any benefit right now. 

I used a slightly different algo for getLedgerToReplicate, to avoid pulling in guava just yet, though we will probably end up pulling it in anyhow.
                
> Recording of underreplication of ledger entries
> -----------------------------------------------
>
>                 Key: BOOKKEEPER-246
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-246
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-client, bookkeeper-server
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-246.diff, BOOKKEEPER-246.diff, BOOKKEEPER-246.diff
>
>
> This JIRA is to decide how to record that entries in a ledger are underreplicated. 
> I think there is a common understanding (correct me if im wrong), that rereplication can be broken into two logically distinct phases. A) Detection of entry underreplication & B) Rereplication. 
> This subtask is to handle the interaction between these two stages. Stage B needs to know what to rereplicate; how should Stage A inform it?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira