Karthik Kambatla commented on YARN-3860:

I am not convinced we need this.

The only reason we don't want both RMs to be active is to avoid the split-brain 
situation. Today, if both RMs become active, one of them fails to create the 
fencing-node and should automatically transition to standby.

> rmadmin -transitionToActive should check the state of non-target node
> ---------------------------------------------------------------------
>                 Key: YARN-3860
>                 URL: https://issues.apache.org/jira/browse/YARN-3860
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: Masatake Iwasaki
>            Assignee: Masatake Iwasaki
>             Fix For: 2.8.0
>         Attachments: YARN-3860.001.patch, YARN-3860.002.patch, 
> YARN-3860.003.patch
> Users can make both ResouceManagers active by {{rmadmin -transitionToActive}} 
> even if {{\--forceactive}} option is not given. {{haadmin 
> -transitionToActive}} of HDFS checks whether non-target nodes are already 
> active but {{rmadmin -transitionToActive}} does not do.

This message was sent by Atlassian JIRA

Reply via email to