[
https://issues.apache.org/jira/browse/YARN-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193549#comment-16193549
]
Hudson commented on YARN-7285:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13035 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13035/])
YARN-7285. ContainerExecutor always launches with priorities due to
(naganarasimha_gr: rev d0046bb5c6919c9620ffa5330eb37b39484151ad)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestLinuxContainerExecutorWithMocks.java
> ContainerExecutor always launches with priorities due to yarn-default property
> ------------------------------------------------------------------------------
>
> Key: YARN-7285
> URL: https://issues.apache.org/jira/browse/YARN-7285
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.8.0, 2.9.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Minor
> Fix For: 2.9.0, 2.8.3, 3.1.0
>
> Attachments: YARN-7285.001.patch, YARN-7285.002.patch
>
>
> ContainerExecutor will launch containers with a specified priority if a
> priority adjustment is specified, otherwise with the OS default priority if
> it is unspecified. YARN-3069 added
> yarn.nodemanager.container-executor.os.sched.priority.adjustment to
> yarn-default.xml, so it is always specified even if the user did not
> explicitly set it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
