[
https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896884#comment-13896884
]
Karthik Kambatla commented on YARN-986:
---------------------------------------
By the way, without this fix in place, the status of running Oozie jobs against
RM HA is as follows. Thanks [~wypoon] for testing this out.
Secure cluster:
* no ha.id in yarn-site.xml on oozie server:
job-tracker set to
** cluster id -> job fails
** host:port of active RM -> job succeeds
** host:port of standby RM -> job fails
* ha.id set to id of active RM in yarn-site.xml on oozie server:
job-tracker set to
** cluster id -> job succeeds
** host:port of active RM -> job succeeds
** host:port of standby RM -> job succeeds
* ha.id set to id of standby RM in yarn-site.xml on oozie server:
job-tracker set to
** cluster id -> job fails
** host:port of active RM -> job fails
** host:port of standby RM -> job fails
Non-secure cluster:
* no ha.id in yarn-site.xml on oozie server:
job-tracker set to
** cluster id -> job fails
** host:port of active RM -> job succeeds
** host:port of standby RM -> job succeeds
* ha.id set to id of active RM in yarn-site.xml on oozie server:
job-tracker set to
** cluster id -> job succeeds
** host:port of active RM -> job succeeds
** host:port of standby RM -> job succeeds
* ha.id set to id of standby RM in yarn-site.xml on oozie server:
job-tracker set to
** cluster id -> job succeeds
** host:port of active RM -> job succeeds
** host:port of standby RM -> job succeeds
In no case does the RM die. (That's good.)
> YARN should use cluster-id as token service address
> ---------------------------------------------------
>
> Key: YARN-986
> URL: https://issues.apache.org/jira/browse/YARN-986
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Karthik Kambatla
>
> This needs to be done to support non-ip based fail over of RM. Once the
> server sets the token service address to be this generic ClusterId/ServiceId,
> clients can translate it to appropriate final IP and then be able to select
> tokens via TokenSelectors.
> Some workarounds for other related issues were put in place at YARN-945.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
