[
https://issues.apache.org/jira/browse/BOOKKEEPER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532079#comment-13532079
]
Uma Maheswara Rao G commented on BOOKKEEPER-293:
------------------------------------------------
Sorry for the delay in review!
{noformat}
patching file bookkeeper-server/src/main/java/org/apache/bookkeeper/replication/
Auditor.java
Hunk #1 succeeded at 25 with fuzz 2.
Hunk #2 FAILED at 79.
Hunk #3 succeeded at 125 (offset -6 lines).
Hunk #4 FAILED at 171.
Hunk #5 succeeded at 178 (offset -8 lines).
Hunk #6 succeeded at 259 (offset -8 lines).
Hunk #7 succeeded at 393 with fuzz 2 (offset -14 lines).
{noformat}
Patch does not apply cleanly for me. This is may be because of recent changes.
We have to rebase it on latest trunk.
> Periodic checking of ledger replication status
> ----------------------------------------------
>
> Key: BOOKKEEPER-293
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-293
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments:
> 0002-BOOKKEEPER-293-Periodic-checking-of-ledger-replicati.patch
>
>
> We should periodically check all ledgers to make sure that they are fully
> replicated.
--
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
