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 Fri, 28 Sep 2012 01:21: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:
-----------------------------------------

          Component/s: resourcemanager
    Affects Version/s: 0.23.3
              Summary: ClientTokens should be per app-attempt and be unregistered on App-finish.
 (was: ClientTokens should be per app-attempt and be unregisterd on App-finish.)
    
> 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
>
> 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

Mime
View raw message