[
https://issues.apache.org/jira/browse/BOOKKEEPER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532521#comment-13532521
]
Uma Maheswara Rao G commented on BOOKKEEPER-293:
------------------------------------------------
Thanks Ivan for the explanation! Even after applying BK-496, it failed to apply
for me.
I am ok with your explanation here regarding scan load, as target bookies will
be in distributed way. I think #b should be a simple option. Anyway we will
discuss that improvement in 4.3
One comment from me is, how about treating AUDITOR_PERIODIC_CHECK_INTERVAL=-1
(or) 0 as disabled this feature. Because this may not really help in some cases
like namenode shared storage as the ledger lifetime it self will be 1 hour in
namenode case, but here scanning period will be 1 day. other than that +1 from
me to push this in.
> 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:
> 0001-BOOKKEEPER-293-Periodic-checking-of-ledger-replicati.patch,
> 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
