hadoop-yarn-issues mailing list archives

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

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

Alejandro Abdelnur commented on YARN-279:
-----------------------------------------

bq. how would you determine upon submission if the tokens will be valid until the AM is launched?

Well, reasonable time (that is the point of the 6 months), if they are not valid when the
AM starts, AM should fail.

Bq. Snappy back,....

Agree that we should have a single piece of code to handle all tokens logic. And it should
be in commons for all to use.

                
> 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