[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294839#comment-13294839
]
Rakesh R commented on BOOKKEEPER-272:
-------------------------------------
Its just suggestion only. I think will see whether any advantage in using
failedbookies information during detection logic BOOKKEEPER-247 JIRA.
>From Auditor side, anyway it needs the data version logic to address the race
>condition mentioned in our above comments. So the auditor is publishing the
>underreplicated ledgerIds and the metadata looks like:
>> LedgerId with failedbookie details as comma separated data.
Example:
/ledgers/auditor/underreplicated/L0001 (data as -> Metadataversion, BK1, BK2)
/ledgers/auditor/underreplicated/L0002 (data as -> Metadataversion, BK1, BK2)
/ledgers/auditor/underreplicated/L0003 (data as -> Metadataversion, BK1, BK2)
> 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
