[
https://issues.apache.org/jira/browse/BOOKKEEPER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445658#comment-13445658
]
Rakesh R commented on BOOKKEEPER-293:
-------------------------------------
We had a discussion in BOOKKEEPER-126 -
[comment|https://issues.apache.org/jira/browse/BOOKKEEPER-126?focusedCommentId=13242095&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13242095],
about the disk corruption.
We were thinking of periodic scanning of ledgers by each bookies(as it will be
local disk scanning and there will not be huge network calls when there are
many ledgers) and will try to re-replicate himself from the peer bookie. Since
we introduced the concept of dedicated auditor process to know the failures,
its good idea to give responsibility of scanning to these periodically.
Also, its good idea to have sub auditors to distribute the load of scanning.
> 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
> Fix For: 4.2.0
>
>
> 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
