[
https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18658:
--------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master and branch-2. Thanks for reviews lads.
> Purge hokey hbase Service implementation; use (internal) Guava Service instead
> ------------------------------------------------------------------------------
>
> Key: HBASE-18658
> URL: https://issues.apache.org/jira/browse/HBASE-18658
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0-alpha-3
>
> Attachments: HBASE-18658.master.001.patch,
> HBASE-18658.master.002.patch, HBASE-18658.master.002.patch,
> HBASE-18658.master.003.patch
>
>
> Purge useless hbase Service class. Having it around only confuses. Purge it
> here because we thought it might be of use fixing parent issue but it only
> confused the issue. And now it is safe to use Guava Service with its nice
> supporting facility (including ServiceManager for running many at a time).
> Introduces "hbase.master.wait.on.service.seconds", a new config. for how long
> Master should wait on a Service to start or stop.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
