[
https://issues.apache.org/jira/browse/YARN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537875#comment-13537875
]
Alejandro Abdelnur commented on YARN-279:
-----------------------------------------
Regarding pushing down the token management to the AM.
Why not use the '6 months passport validity rule'? In other words, require, on
submission that any delegation token being used must at least last until the AM
is up and running, else things would fail. Once the AM is up and running it is
the AM responsibility to renew it.
> 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
