[
https://issues.apache.org/jira/browse/HBASE-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434343#comment-13434343
]
Jesse Yates commented on HBASE-6571:
------------------------------------
@Andrew
bq. We should not have two error notification frameworks (this and Abortable)
coexisting for long.
I'd argue that we can have both, but we can wrap the abortable code (which is a
nice abstraction) into the general framework.
> Generic multi-thread/cross-process error handling framework
> -----------------------------------------------------------
>
> Key: HBASE-6571
> URL: https://issues.apache.org/jira/browse/HBASE-6571
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Attachments: Distributed Error Monitoring.docx,
> java_HBASE-6571-v0.patch
>
>
> The idea for a generic inter-process error-handling framework came from
> working on HBASE-6055 (snapshots). Distributed snapshots require tight time
> constraints in taking a snapshot to minimize offline time in face of errors.
> However, we often need to coordinate errors between processes and the current
> Abortable framework is not sufficiently flexible to handle the multitude of
> situations that can occur when coordinating between all region servers, the
> master and zookeeper. Using this framework error handling for snapshots was a
> simple matter, amounting to maybe 200 LOC.
> This seems to be a generally useful framework and can be used to easily add
> inter-process error handling in HBase. The most obvious immediate usage is as
> part of HBASE-5487 when coordinating multiple sub-tasks.
--
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
