[
https://issues.apache.org/jira/browse/BOOKKEEPER-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983229#comment-13983229
]
Rakesh R commented on BOOKKEEPER-749:
-------------------------------------
As compared to the earlier, now the plan is to go with polling approach if
there is atleast one urledger is available to re-replicate irrespective of lock
failures. Will you be able to incorporate the notifyUnderreplicationChange() in
BOOKKEEPER-746.
> Improve LedgerUnderreplicationManager#getLedgerToRereplicate()
> --------------------------------------------------------------
>
> Key: BOOKKEEPER-749
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-749
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-auto-recovery
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: 00001-BOOKKEEPER-749-interface.patch
>
>
> As per the discussion in BOOKKEEPER-733,
> LedgerUnderreplicationManager#getLedgerToRereplicate having multiple
> resposibilities like : getUrLedger + acquireLock. Actually the idea of this
> JIRA is to make the interface better.
> Please see the discussion thread:
> https://issues.apache.org/jira/browse/BOOKKEEPER-733?focusedCommentId=13963072&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13963072
--
This message was sent by Atlassian JIRA
(v6.2#6252)
