[jira] [Commented] (BOOKKEEPER-272) Provide automatic mechanism to know bookie failures

["Rakesh R (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436765#comment-13436765 ] 

Rakesh R commented on BOOKKEEPER-272:
-------------------------------------

Thanks Ivan,Uma,Flavio for your thoughts. It would be great if others could review my changes.


Following are the changes made in the latest patch:
- by considering Ivan's point, provided AutoRecoveryManager#start() and #stop() methods and removed the dependency with Bookie server. Anyone can plugin the service by invoking start() and stop() operational methods.
- I've raised another JIRA BOOKKEEPER-319 to finalize the way to manage the recovery service. 
- also corrected ZkLedgerUnderreplicationManager.java, where adding duplicate 'missingreplica' in case of an underreplicated ledger contains multiple bookie failures.

+Note:+ This patch has dependency with BOOKKEEPER-304 and to be applied after BOOKKEEPER-304 patch


                
> 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.3.patch, BOOKKEEPER-272.Auditor.1.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