hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
Date Thu, 24 Aug 2017 05:23:00 GMT

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

stack commented on HBASE-18658:

.003 Fix tests. Failures were legit. Starting a Service implementation, we were checking for

> 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,
> 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

View raw message