[
https://issues.apache.org/jira/browse/BOOKKEEPER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530680#comment-13530680
]
Uma Maheswara Rao G commented on BOOKKEEPER-293:
------------------------------------------------
As per the readmap listed
[here|https://cwiki.apache.org/BOOKKEEPER/roadmap.html], this should be a
blocker. Because if you see second point '•autorecovery (bookie and ledger)'
1) bookie autorecovery : already addressed by other subtasks here
2) ledger autorecovery : one way detecting the corruptions while
writing/reading is handled by BOOKKEEPER-199, but that will not do any recovery
job automatically after detecting disk failures.
In namenode case, anyway this JIRA will not help as the period of scanning
should be much higher here and we can not scan so frequently. In namenode,
ledger lifetime will be checkpoint time(1hour) only.
Considering other side effects of this JIRA approach now (listed in my
comment), I am ok to move this to 4.3 and discuss cleanly. What about others
opinion here?
> 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
