You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Yufei Gu (JIRA)" <ji...@apache.org> on 2017/06/22 23:53:01 UTC
[jira] [Comment Edited] (YARN-6625) yarn application -list returns
a tracking URL for AM that doesn't work in secured and HA environment
[ https://issues.apache.org/jira/browse/YARN-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060140#comment-16060140 ]
Yufei Gu edited comment on YARN-6625 at 6/22/17 11:52 PM:
----------------------------------------------------------
Thanks [~rkanter] for the review. I uploaded patch v2 as our off-line discussion.
First, we don't use the solution in patch v1 since it is not a good idea to let AM access the Admin service of RM. Second, AM cannot get RM HA status thought scheduler service since there is no scheduler service in a standby RM.
Patch v2 provide a solution which try RMs one by one until we find one alive RM based on the assumption that it doesn't matter if RM is active or standby in this situation since if AM redirect to a standby RM, the standby RM will do redirect to active RM anyway. The only concern is that we should make sure the RM is alive.
was (Author: yufeigu):
Thanks [~rkanter] for the review. I uploaded patch v2 as our off-line discussion.
First, we don't use the solution in patch v1. Seems like it is not a good idea to let AM access the Admin service of RM. Meanwhile, AM cannot get RM HA status thought scheduler service since there is no scheduler service in a standby RM.
Patch v2 provide a solution which try RMs one by one until we find one alive RM based on the assumption that it doesn't matter if RM is active or standby in this situation since if AM redirect to a standby RM, the standby RM will do redirect to active RM anyway. The only concern is that we should make sure the RM is alive.
> yarn application -list returns a tracking URL for AM that doesn't work in secured and HA environment
> ----------------------------------------------------------------------------------------------------
>
> Key: YARN-6625
> URL: https://issues.apache.org/jira/browse/YARN-6625
> Project: Hadoop YARN
> Issue Type: Bug
> Components: amrmproxy
> Affects Versions: 3.0.0-alpha2
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: YARN-6625.001.patch, YARN-6625.002.patch
>
>
> The tracking URL given at the command line should work secured or not. The tracking URLs are like http://node-2.abc.com:47014 and AM web server supposed to redirect it to a RM address like this http://node-1.abc.com:8088/proxy/application_1494544954891_0002/, but it fails to do that because the connection is rejected when AM is talking to RM admin service to get HA status.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org