hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-279) Generalize RM token management
Date Fri, 21 Dec 2012 15:15:12 GMT

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

Daryn Sharp commented on YARN-279:
----------------------------------

The problem with the passport idea is how would you determine upon submission if the tokens
will be valid until the AM is launched?  It's non-deterministic how long the RM will take
to launch the job after submission.  You also have the problem that the yarn framework may
need to use the tokens itself (ie. log aggregation) so it can't purely be the responsibility
of the AM to renew/cancel.

Snapping back, the larger problem is that renewing tokens requires the jar for that project
to be in the CLASSPATH.  I don't think that's a reasonable requirement for either the RM or
AM, since neither is in the position to know what jars are required for external token-based
systems that will be accessed by the task.  
                
> Generalize RM token management
> ------------------------------
>
>                 Key: YARN-279
>                 URL: https://issues.apache.org/jira/browse/YARN-279
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.5
>            Reporter: Daryn Sharp
>
> Token renewal/cancelation in the RM presents challenges to support arbitrary tokens.
 The RM's CLASSPATH is currently required to have token renewer classes and all associated
classes for the project's client.  The logistics of having installs on the RM of all hadoop
projects that submit jobs - just to support client connections to renew/cancel tokens - are
untenable.

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