[
https://issues.apache.org/jira/browse/YARN-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-134:
-----------------------------------------
Attachment: YARN-134-20120927.txt
This patch fixes this, and much more.
- Separated AMSecretManager into the RM and AM specific classes.
- To address this specific bug, AMClientTokenSecretManager doesn't create keys
anymore for each request, it does it only once per AM.
- Added a test verifying the functionality of client-tokens.
Note that there are other things that need to be done:
- ClientTokens are per app-attempt but are created per app. An existing bug.
- Apps don't get unregistered from RMClientTokenSecretManager. This was the
case before too and can be fixed together with issue (1).
Plan to fix the above issues separately in a follow up JIRA, don't want to
bloat this one.
> ClientToAMSecretManager creates keys without checking for validity of the
> appID
> -------------------------------------------------------------------------------
>
> Key: YARN-134
> URL: https://issues.apache.org/jira/browse/YARN-134
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 0.23.4, 2.0.3-alpha
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Attachments: YARN-134-20120927.txt
>
>
--
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
