[
https://issues.apache.org/jira/browse/YARN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547246#comment-13547246
]
Hadoop QA commented on YARN-320:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12563814/YARN-320.patch
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 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/325//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/325//console
This message is automatically generated.
> RM should always be able to renew its own tokens
> ------------------------------------------------
>
> Key: YARN-320
> URL: https://issues.apache.org/jira/browse/YARN-320
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: YARN-320.branch-23.patch, YARN-320.branch-23.patch,
> YARN-320.patch
>
>
> YARN-280 introduced fast-fail for job submissions with bad tokens.
> Unfortunately, other stack components like oozie and customers are acquiring
> RM tokens with a hardcoded dummy renewer value. These jobs would fail after
> 24 hours because the RM token couldn't be renewed, but fast-fail is failing
> them immediately. The RM should always be able to renew its own tokens
> submitted with a job. The renewer field may continue to specify an external
> user who can renew.
--
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
