[jira] [Updated] (YARN-2807) Option "--forceactive" not works as described in usage of "yarn rmadmin -transitionToActive"

["Masatake Iwasaki (JIRA)" <ji...@apache.org>]

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

Masatake Iwasaki updated YARN-2807:
-----------------------------------
    Attachment: YARN-2807.2.patch

Thanks for the comment [~ajisakaa]. I rethinked about this and left --forcemanual undocumented as intended in the usage of HAAdmin because it is dangerous especially for HDFS. I just added description about --forcemanual in the site document of YARN.

> Option "--forceactive" not works as described in usage of "yarn rmadmin -transitionToActive"
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-2807
>                 URL: https://issues.apache.org/jira/browse/YARN-2807
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Priority: Critical
>         Attachments: YARN-2807.1.patch, YARN-2807.2.patch
>
>
> Currently the help message of "yarn rmadmin -transitionToActive" is:
> {code}
> transitionToActive: incorrect number of arguments
> Usage: HAAdmin [-transitionToActive <serviceId> [--forceactive]]
> {code}
> But the --forceactive not works as expected. When transition RM state with --forceactive:
> {code}
> yarn rmadmin -transitionToActive rm2 --forceactive
> Automatic failover is enabled for org.apache.hadoop.yarn.client.RMHAServiceTarget@64c9f31e
> Refusing to manually manage HA state, since it may cause
> a split-brain scenario or other incorrect state.
> If you are very sure you know what you are doing, please
> specify the forcemanual flag.
> {code}
> As shown above, we still cannot transitionToActive when automatic failover is enabled with --forceactive.
> The option can work is: {{--forcemanual}}, there's no place in usage describes this option. I think we should fix this



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)