[
https://issues.apache.org/jira/browse/BOOKKEEPER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440178#comment-13440178
]
Ivan Kelly commented on BOOKKEEPER-248:
---------------------------------------
For completeness could you add a sync BookKeeperAdmin#openLedger. Should be
almost a copy/paste. Otherwise patch is good.
Regarding Service, im fine with leaving that until later. We also need to think
about how we run the threads. For example, it would be nice for the threads to
be able to restart if they crash, but only after a delay and only for a limit
number of times (to stop a persistent failure filling everything with logs). I
think hbase does something like this now, so will look and see.
> Rereplicating of under replicated data
> --------------------------------------
>
> Key: BOOKKEEPER-248
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-248
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Ivan Kelly
> Assignee: Uma Maheswara Rao G
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-248.patch, BOOKKEEPER-248.patch
>
>
> This subtask discusses how we will rereplicate underreplicated entries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
