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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/10/08 23:44:03 UTC

[jira] [Updated] (YARN-134) ClientToAMSecretManager creates keys without checking for validity of the appID

     [ 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-20121008.txt

Tx for the review, Sid.

Here's an updated patch.
 - Got rid of the logs
 - Renamed RMClientTokenSecretManager to ClientToAMTokenSecretManagerInRM and AMClientTokenSecretManager to ClientToAMTokenSecretManager.
                
> 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.3
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: YARN-134-20120927.txt, YARN-134-20121008.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