Apache/hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

YARN-7285. ContainerExecutor always launches with priorities due to yarn-default property. Contributed by Jason Lowe.

Browse Source 
(cherry picked from commit d0046bb5c6919c9620ffa5330eb37b39484151ad)
This commit is contained in:
Naganarasimha 2017-10-06 00:06:25 +05:30
parent 935ef1c24e
commit d4cd8ccb5d
2 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
View File

@ -1654,10 +1654,10 @@
<property>
<description>
Adjustment to the container OS scheduling priority. In Linux, passed
directly to the nice command.
directly to the nice command. If unspecified then containers are launched
without any explicit OS priority.
</description>
<name>yarn.nodemanager.container-executor.os.sched.priority.adjustment</name>
<value>0</value>
</property>
<property>

3
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestLinuxContainerExecutorWithMocks.java
View File

@ -237,9 +237,6 @@ public void testLaunchCommandWithoutPriority() throws IOException {
// make sure the command doesn't contain the nice -n since priority
// not specified
List<String> command = new ArrayList<String>();
Configuration conf = mockExec.getConf();
conf.unset(YarnConfiguration.NM_CONTAINER_EXECUTOR_SCHED_PRIORITY);
mockExec.setConf(conf);
mockExec.addSchedPriorityCommand(command);
assertEquals("addSchedPriority should be empty", 0, command.size());
}