[YARN-7285] ContainerExecutor always launches with priorities due to yarn-default property

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.0, 2.9.0
• Fix Version/s: 2.9.0, 2.8.3, 3.1.0
• Component/s: nodemanager
• Target Version/s: 2.9.0, 2.8.3, 3.0.0
• Hadoop Flags: Reviewed
• Assignee: Jason Darrell Lowe
• Reporter: Jason Darrell Lowe
• Created: 03/Oct/17 19:39
• Updated: 05/Oct/17 20:01
• Resolved: 05/Oct/17 19:08

Description

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.

Issue Links

• is broken by: YARN-3069 Document missing properties in yarn-default.xml
• relates to: YARN-5444 Fix failing unit tests in TestLinuxContainerExecutorWithMocks