hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701
Date Fri, 26 Jul 2013 23:19:49 GMT

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

Bikas Saha commented on YARN-937:

We can keep my suggestion and remove the translation code from YARNClient now. Things should
continue to work if we simply remove that code since the token already has the address and
there is no need to re-populate it. 

Or we can continue to keep the config address lookup code in YarnClientImpl. Later, when we
improve RMProxy to do the right thing, we will have to remember to come back and remove this

Your call.


> Fix unmanaged AM in non-secure/secure setup post YARN-701
> ---------------------------------------------------------
>                 Key: YARN-937
>                 URL: https://issues.apache.org/jira/browse/YARN-937
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Arun C Murthy
>            Assignee: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 2.1.0-beta
>         Attachments: YARN-937.patch, YARN-937.patch, YARN-937.patch, YARN-937.patch,
YARN-937.patch, YARN-937.patch
> Fix unmanaged AM in non-secure/secure setup post YARN-701 since app-tokens will be used
in both scenarios.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message