hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-135) ClientTokens should be per app-attempt and be unregistered on App-finish.
Date Fri, 19 Oct 2012 21:00:14 GMT

    [ https://issues.apache.org/jira/browse/YARN-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480385#comment-13480385

Hadoop QA commented on YARN-135:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 6 new or modified
test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/102//console

This message is automatically generated.
> 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, YARN-135-20121019.1.txt, YARN-135-20121019.2.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