[
https://issues.apache.org/jira/browse/HBASE-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885278#action_12885278
]
Todd Lipcon commented on HBASE-2696:
------------------------------------
bq. As for InterruptedException, this is always one of those special things. It
will get clunky if we let them out of all the methods, can we get away with
just returning null/false values and logging the exception?
If you let interruption pass through, you should do
Thread.currentThread().interrupt() to maintain interruption status.
> ZooKeeper cleanup and refactor
> ------------------------------
>
> Key: HBASE-2696
> URL: https://issues.apache.org/jira/browse/HBASE-2696
> Project: HBase
> Issue Type: Sub-task
> Components: master, regionserver, zookeeper
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Priority: Critical
> Fix For: 0.21.0
>
> Attachments: HBASE-2696-part1-NewClasses_NotIntegrated.patch,
> HBASE-2696-part1-v2-NewClasses_NotIntegrated.patch,
> HBASE-2696-part1-v3-NewClasses_RS.patch,
> HBASE-2696-part1-v4-NewClasses_RS_Tested.patch
>
>
> Currently almost everything we do with ZooKeeper is stuffed into a single
> class {{ZookeeperWrapper}}.
> This issue will deal with cleaning up our usage of ZK, adding some new
> abstractions to help with the master changes, splitting up watchers from
> utility methods, and nailing down the contracts of our ZK methods with
> respect to setting watchers, throwing exceptions, etc...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
