[YARN-6344] Add parameter for rack locality delay in CapacityScheduler

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha4
• Component/s: capacityscheduler
• Hadoop Flags: Reviewed
• Assignee: Konstantinos Karanasos
• Reporter: Konstantinos Karanasos
• Created: 15/Mar/17 19:37
• Updated: 01/Nov/18 05:07
• Resolved: 30/Jun/17 00:27

Description

When relaxing locality from node to rack, the node-locality-parameter is used: when scheduling opportunities for a scheduler key are more than the value of this parameter, we relax locality and try to assign the container to a node in the corresponding rack.

On the other hand, when relaxing locality to off-switch (i.e., assign the container anywhere in the cluster), we are using a localityWaitFactor, which is computed based on the number of outstanding requests for a specific scheduler key, which is divided by the size of the cluster.
In case of applications that request containers in big batches (e.g., traditional MR jobs), and for relatively small clusters, the localityWaitFactor does not affect relaxing locality much.
However, in case of applications that request containers in small batches, this load factor takes a very small value, which leads to assigning off-switch containers too soon. This situation is even more pronounced in big clusters.
For example, if an application requests only one container per request, the locality will be relaxed after a single missed scheduling opportunity.

The purpose of this JIRA is to rethink the way we are relaxing locality for off-switch assignments.

Issue Links

• duplicates: YARN-6289 Fail to achieve data locality when runing MapReduce and Spark on HDFS
• is related to: YARN-8965 Revisit delay scheduling for cloud environment
• is related to: YARN-4287 Capacity Scheduler: Rack Locality improvement