[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Attachment: HBASE-18658.master.001.patch > 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 > > > 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). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Hadoop Flags: Reviewed Status: Patch Available (was: Open) > 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 > > > 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). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Attachment: HBASE-18658.master.002.patch > 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 > > > 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). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Attachment: HBASE-18658.master.002.patch Retry. Failures seem unrelated. > 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). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Description: 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. was: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). > 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 (v6.4.14#64029)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Attachment: HBASE-18658.master.003.patch > 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)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ 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)
[jira] [Updated] (HBASE-18658) Purge hokey hbase Service implementation; use (internal) Guava Service instead
[ https://issues.apache.org/jira/browse/HBASE-18658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18658: -- Fix Version/s: 2.0.0 > 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 >Priority: Major > Fix For: 2.0.0-alpha-3, 2.0.0 > > 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 (v7.6.3#76005)
