[ 
https://issues.apache.org/jira/browse/YARN-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15784070#comment-15784070
 ] 

Daniel Templeton commented on YARN-5685:
----------------------------------------

I would look at it the other way around.  The default assumption should be 
embedded leader election.  If an out-of-process election is added, it will be 
the new and different thing, and it should then have a config param that 
enables it.  Today with no alternative, having a config param for embedded 
makes no sense.  The two options are: cluster works and cluster broken.

If you're really convinced that leadership election is something that will 
change again soon, then I'd still deprecate the embedded option and add a new 
option that selects the election type: "embedded" or "external", with the 
"external" value only added once that's actually a thing.  Heck, throw in 
"manual" as a valid value, and we can also deprecate the config param to enable 
automatic failover.

> Non-embedded HA failover is broken
> ----------------------------------
>
>                 Key: YARN-5685
>                 URL: https://issues.apache.org/jira/browse/YARN-5685
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.9.0, 3.0.0-alpha1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>            Priority: Critical
>              Labels: oct16-hard
>         Attachments: YARN-5685.001.patch, YARN-5685.002.patch
>
>
> If HA is enabled with automatic failover enabled and embedded failover 
> disabled, all RMs all come up in standby state.  To make one of them active, 
> the {{--forcemanual}} flag must be used when manually triggering the state 
> change.  Should the active go down, the standby will not become active and 
> must be manually transitioned with the {{--forcemanual}} flag.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to