[jira] [Commented] (HBASE-7047) [snapshots] Refactor error handling to use javax.management

["Jonathan Hsieh (JIRA)" <ji...@apache.org>]

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

Jonathan Hsieh commented on HBASE-7047:
---------------------------------------

Jesse, can you post a link to a review board version of this patch?  Thanks.
                
> [snapshots] Refactor error handling to use javax.management
> -----------------------------------------------------------
>
>                 Key: HBASE-7047
>                 URL: https://issues.apache.org/jira/browse/HBASE-7047
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, master, regionserver, snapshots, Zookeeper
>    Affects Versions: hbase-6055
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: hbase-6055
>
>         Attachments: hbase-7047-v0-adv.patch, hbase-7047-v0.patch
>
>
> The current error handling framework introduced in HBASE-6571 adds a lot of complexity for what is essentially a solved problem. Specifically, cross-thread notifications have been generalized for the JMX tooling in the javax.management classes. 
> Similar to what we developed, they have a NotifciationBroadcaster, NotificationListener, etc. though these are interfaces rather than general classes. These javax classes can be used almost 1-to-1 as replacements for things like the ExceptionOrchestrator and ExceptionListener. This also gives us the opportunity to easily add primitive notifications for standard HBase things like (1) timeouts, (2) aborts, and (3) server stops since the framework already considers things like typed notifications. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira