[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294548#comment-13294548
]
Rakesh R commented on BOOKKEEPER-272:
-------------------------------------
Oh, seems that I did't explain clearly at my comment.
{quote}
Im not sure what you mean here. Having the failed bookie stored in the data is
useful for debugging purposes, but we should do a check on the ledger
beforehand anyhow to determine what to recover. Are you trying to avoid another
read to the ledger znode?
{quote}
My point is, rather than reading with bookieclient and finding the badReplicas,
why don't we find the fragments using the ledgermetadata present in zookeeper
as we already knows the failed bookie.
> Provide automatic mechanism to know bookie failures
> ---------------------------------------------------
>
> Key: BOOKKEEPER-272
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-272
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: BOOKKEEPER-272.1.patch, BOOKKEEPER-272.2.patch,
> BOOKKEEPER-272.Auditor.patch
>
>
> The idea is to build automatic mechanism to find out the bookie failures.
> Setup the bookie failure notifications to start the re-replication process.
> There are multiple approaches to findout bookie failures. Please refer the
> documents attached in BookKeeper-237.
--
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
