You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2013/09/09 22:46:54 UTC

[jira] [Updated] (HADOOP-9945) HAServiceState should have a state for stopped services

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

Karthik Kambatla updated HADOOP-9945:
-------------------------------------

    Attachment: hadoop-9945-1.patch

Attaching a trivial patch to add the STOPPED state.

Haven't added any tests. Plan to test the functionality in 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
>         Attachments: hadoop-9945-1.patch
>
>
> HAServiceState, currently, has states for Initializing, Active, and Standby. 
> For RM HA, it is useful to have another state "STOPPED". 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