You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2012/12/20 09:39:12 UTC

[jira] [Updated] (YARN-50) Implement renewal / cancellation of Delegation Tokens

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

Siddharth Seth updated YARN-50:
-------------------------------

    Attachment: YARN-50_wip.txt

Work in progress. Some of the classes can be moved to different packages. Needs to be tested.

One flaw with renewing tokens in their current form in the RM, is that the RM ends up depending on the token Renewers to be in the classpath.
HDFS token renewal already needs the HDFS renewer (DFSClient.Renewer) to be in the RM classpath.
With this patch, MR JobHistoryServer token renewal requires MR jars in the RM classpath. (The patch does not add them - but the default startup scripts already do). It also ends up requiring HistoryServer configuration parameters to be part of the RM configuration.
Avoiding these dependencies doesn't seem like it'll be a small change.
                
> Implement renewal / cancellation of Delegation Tokens
> -----------------------------------------------------
>
>                 Key: YARN-50
>                 URL: https://issues.apache.org/jira/browse/YARN-50
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: YARN-50_wip.txt
>
>
> Currently, delegation tokens issues by the RM and History server cannot be renewed or cancelled. This needs to be implemented.

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