hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-9945) HAServiceState should have a state for stopped services
Date Mon, 09 Sep 2013 20:58:54 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Karthik Kambatla resolved HADOOP-9945.

          Resolution: Duplicate
    Target Version/s:   (was: 2.1.1-beta)

Resolving this as Duplicate, and fixing it as part of YARN-1027.
> HAServiceState should have a state for stopped services
> -------------------------------------------------------
>                 Key: HADOOP-9945
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9945
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Minor
>         Attachments: hadoop-9945-1.patch
> HAServiceState, currently, has states for Initializing, Active, and Standby. 
> For RM HA, it is useful to have another state "STOPPING". This is because YARN has a
separate service model where Services are stopped and can't be restarted. When the Active/Standby
RM is stopped, it can no longer go back to the Active/Standby state; setting the HAServiceState
to Initializing is misleading.

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

View raw message