[
https://issues.apache.org/jira/browse/HBASE-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HBASE-7047:
-------------------------------
Attachment: hbase-7047-v0-adv.patch
Attaching 'advanced' version of v0 that does some more advanced refactoring of
the offline snapshot handler to take advantage of the new framework.
Specifically, uses a centralized notification 'hub' to track the running
handler and then uses the added StopNotification to pass a 'stop' update to the
running DisabledTableSnapshotHandler. This is really nice in that it is
basically zero overhead to running multiple snapshots or adapting for stopping
a running snapshot and any restores.
> [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, java_6667-v0.txt
>
>
> 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