[YARN-443] allow OS scheduling priority of NM to be different than the containers it launches

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha, 0.23.6
• Fix Version/s: 0.23.7, 2.0.4-alpha
• Component/s: nodemanager
• Target Version/s: 0.23.7, 2.1.0-beta
• Assignee: Thomas Graves
• Reporter: Thomas Graves
• Created: 01/Mar/13 21:02
• Updated: 27/Oct/14 18:37
• Resolved: 08/Mar/13 14:55

Description

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.

Issue Links

• is related to: MAPREDUCE-4058 adjustable task priority

Sub-Tasks

• allow OS scheduling priority of NM to be different than the containers it launches for Windows: Open