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] [Resolved] (MAPREDUCE-4069) Cleanup task tokens interface
Date Thu, 13 Jun 2013 20:25:20 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vinod Kumar Vavilapalli resolved MAPREDUCE-4069.

    Resolution: Duplicate

Fixed by MAPREDUCE-5199.
> Cleanup task tokens interface
> -----------------------------
>                 Key: MAPREDUCE-4069
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4069
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.2
>            Reporter: Jason Lowe
>            Priority: Minor
> This tracks a couple of cleanup issues that were identified in MAPREDUCE-4043:
> * It seems unnecessary to pass the job token and credentials separately when we always
combine the job token into the credentials before building the container launch context. 
The TaskImpl and TaskAttemptImpl constructors could simply take credentials with the job token
already added rather than separate job token and credential parameters.
> * It's unclear whether we still need the appTokens file that is placed into HDFS by the
job submitter, localized by the NM, and finally read in by the AM. I believe the AM's credentials
sent in the AM's container launch context already contains the same information.  If that's
the case, we should remove the code related to the appTokens file.

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