[
https://issues.apache.org/jira/browse/BOOKKEEPER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444840#comment-13444840
]
Uma Maheswara Rao G commented on BOOKKEEPER-325:
------------------------------------------------
I have to handle one more case in that patch. i.e, currently I am simply
fencing after penidng replication timeout if ledger is in open state.
Here we have to recheck whether the fragment still presnts as last fragment or
not. ex: if RW added the ledger to pending replication and client reformed the
ensemble immediately after that. So, the last fragment for that ledger will not
be in under replication, because older fragment will just move one step above
the last fragment. Current last fragment will be newly created ensemble.
Will handle this case in next revision of my patch.
> 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
> Attachments: 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
