[jira] [Updated] (BOOKKEEPER-325) Delay the replication of a ledger if RW found that its last fragment is in underReplication.

["Ivan Kelly (JIRA)" <ji...@apache.org>]

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

Ivan Kelly updated BOOKKEEPER-325:
----------------------------------

    Fix Version/s: 4.2.0
    
> Delay the replication of a ledger if RW found that its last fragment is in underReplication.
> --------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-325
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-325
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-auto-recovery
>    Affects Versions: 4.2.0
>            Reporter: Uma Maheswara Rao G
>            Assignee: Uma Maheswara Rao G
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-325.patch, BOOKKEEPER-325.patch, BOOKKEEPER-325.patch
>
>
> When RW found that ledger's last fragment is in underReplication state, then we should delay that ledger replication for some grace period. optimally we can replicate other fragments.
> The idea is, Whenever it finds the last fragement is under replicated, It can add into PendingReplication list.
> There will be a small daemon, which will check for the timeouts of this ledgers. 
> Once it timed out , it will trigger the normal replication process if it is not in last fragment. Otherwise, it will fence the ledger and will trigger the replication nomally.
> see the discussion for more info:
> http://markmail.org/message/ruhhxxgvuqnjlu2s#query:+page:1+mid:f6ifo4sizulwiaem+state:results

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