[
https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596107#comment-13596107
]
Hadoop QA commented on YARN-443:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572561/YARN-443.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 2 new
or modified test files.
{color:red}-1 one of tests included doesn't have a timeout.{color}
{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-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/476//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/476//console
This message is automatically generated.
> allow OS scheduling priority of NM to be different than the containers it
> launches
> ----------------------------------------------------------------------------------
>
> Key: YARN-443
> URL: https://issues.apache.org/jira/browse/YARN-443
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 2.0.3-alpha, 0.23.6
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Attachments: YARN-443-branch-0.23.patch, YARN-443-branch-0.23.patch,
> YARN-443-branch-2.patch, YARN-443.patch, YARN-443.patch, YARN-443.patch,
> YARN-443.patch
>
>
> It would be nice if we could have the nodemanager run at a different OS
> scheduling priority than the containers so that you can still communicate
> with the nodemanager if the containers out of control.
> On linux we could launch the nodemanager at a higher priority, but then all
> the containers it launches would also be at that higher priority, so we need
> a way for the container executor to launch them at a lower priority.
> I'm not sure how this applies to windows if at all.
--
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
