hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5199) AppTokens file can/should be removed
Date Mon, 20 May 2013 06:51:17 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-5199:
----------------------------------------------------

bq. The issue stems from conf.getCredentials().addAll(credentials). Conf is a JobConf, and
credentials is obtained via the login UGI. These credentials include the app token so by propagating
them into the jobConf, the tasks acquire the app token.
I guess you are referring to such call in MRAppMaster. That conf is *never* propagated to
the tasks, like I said before. The conf that tasks see is the one written out by client.

I still don't understand the problem.

Please share logs or stack traces or a test-case that fails.

I quickly wrote up a patch for YARN-701 and modified TestMRJobs and SleepJob to print out
all credentials - ApplicationToken never goes through to the task like I suspected, either
via UGI or the conf.
                
> AppTokens file can/should be removed
> ------------------------------------
>
>                 Key: MAPREDUCE-5199
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5199
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 3.0.0, 2.0.5-beta
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: MAPREDUCE-5199.patch
>
>
> All the required tokens are propagated to AMs and containers via startContainer(), no
need for explicitly creating the app-token file that we have today..

--
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

Mime
View raw message