[
https://issues.apache.org/jira/browse/YARN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622819#comment-13622819
]
Hadoop QA commented on YARN-525:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12577058/YARN-525.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/671//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/671//console
This message is automatically generated.
> make CS node-locality-delay refreshable
> ---------------------------------------
>
> Key: YARN-525
> URL: https://issues.apache.org/jira/browse/YARN-525
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
> Affects Versions: 2.0.3-alpha, 0.23.7
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Attachments: YARN-525-branch-0.23.patch, YARN-525-branch-0.23.patch,
> YARN-525.patch
>
>
> the config yarn.scheduler.capacity.node-locality-delay doesn't change when
> you change the value in capacity_scheduler.xml and then run yarn rmadmin
> -refreshQueues.
--
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
