[
https://issues.apache.org/jira/browse/YARN-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872514#comment-13872514
]
Bikas Saha commented on YARN-1584:
----------------------------------
And what use case does this solve other than make RM1 become standby? Downside
is a lot of churn in client that are currently using YARN as they switch from
RM1 to RM2? If RM1 is going to go back and join the election anyways then why
are we doing this?
Secondly, I dont see how this works when there are 3 RMs in the leader
election. I dont think we want to restrict our model to only support 2 RMs.
Lastly, isnt this something that can be done entirely on the client side.
Client would first call transitionToStandby() on all RM's other than the one
that the admin want to make active. It will determine if the desired RM has
become active (or timeout) and then make the remaining RMs'
transitionToActive() and rejoin the election.
> Support explicit failover when automatic failover is enabled
> ------------------------------------------------------------
>
> Key: YARN-1584
> URL: https://issues.apache.org/jira/browse/YARN-1584
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.4.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
>
> YARN-1029 adds automatic failover support. However, users can't explicitly
> ask for a failover from one RM to the other without stopping the other RM.
> Stopping the RM until the other RM takes over and then restarting the first
> RM is more involving and exposes the RM-ensemble to SPOF for a longer
> duration.
> It would be nice to allow explicit failover through yarn rmadmin -failover
> command.
> PS: HDFS supports -failover option.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
