[
https://issues.apache.org/jira/browse/BOOKKEEPER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396038#comment-13396038
]
Uma Maheswara Rao G commented on BOOKKEEPER-248:
------------------------------------------------
I have worked on this patch.
ReplicationWorker is a thread which will start the UnderreplicateWatcher for
getting the underreplicated ledgers and populate into underreplicatedLedgersQ.
ReplicationWorker loop will pool for the elements from this Q. Once it picks
the ledger from this Q, it will get the fragments from LedgerChecker. After
that it will try to get the lock. On suceess, it will replicate that fragments
using LedgerFragmentReplicator (updated in BOOKKEEPER-299). Again On
successfull replication, it will clear the lock and delete the
underreplicatedledger node.
We have choosen current node as target node. If the current node is part of the
fragment ensemble, then it will just skip and release lock for giving chance to
other bookies to copy that fragments. Will proceed for picking other ledger.
Will upload Distributed lock patch and Replication worker patches separately...
> Rereplicating of under replicated data
> --------------------------------------
>
> Key: BOOKKEEPER-248
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-248
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server
> Reporter: Ivan Kelly
> Assignee: Uma Maheswara Rao G
>
> This subtask discusses how we will rereplicate underreplicated entries.
--
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
