[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400853#comment-13400853
]
Flavio Junqueira commented on BOOKKEEPER-272:
---------------------------------------------
To summarize an offline discussion I had with Ivan, there are two points that I
raised during the discussion:
# If the bookie and the auditor run on the same jvm, is it possible that
runtime exceptions thrown by the auditor will kill the whole jvm and
consequently the bookie as well?
# If the bookie and the auditor run on the same jvm, it might be more difficult
to debug. In particular, I was wondering about how to separate the log messages
for postmortem analysis and debugging in general.
# The performance of a bookie is more critical than the performance of the
auditor. Running them on separate jvms might improve performance isolation.
> 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.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
