hadoop-yarn-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] [Updated] (YARN-135) ClientTokens should be per app-attempt and be unregistered on App-finish.
Date Sat, 29 Sep 2012 01:31:07 GMT

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

Vinod Kumar Vavilapalli updated YARN-135:

    Attachment: YARN-135-20120928.txt

Attaching a patch. This does the following:
 - Convert the url-encoded ClientToken from a string to its own class.
 - Consolidate the code duplicated across ContainerToken, DelegateToken into a base class
Token and also use the same for ClientToken.
 - Make ClientToken per app-attempt (the focus of this JIRA)
 - Also unregister keys from ClientTokenSecretManager when an app-attempt finishes.
> ClientTokens should be per app-attempt and be unregistered on App-finish.
> -------------------------------------------------------------------------
>                 Key: YARN-135
>                 URL: https://issues.apache.org/jira/browse/YARN-135
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 0.23.3
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: YARN-135-20120928.txt
> Two issues:
>  - ClientTokens are per app-attempt but are created per app.
>  - Apps don't get unregistered from RMClientTokenSecretManager.

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