Hadoop Yarn延迟调度分析（Delay Schedulering）

大规模集群中，对数据本地化（data loality）的优化，可以减少很多网络IO，变成本地的磁盘IO，而磁盘的IO比网络的IO快很多，这对降低集群的IO负载以及增加集群的吞吐量是很有益处的，所以我对Yarn中的延迟调度进行分析，尝试提高作业中任务所在容器的调度本地化命中率。

我们从自带的延迟调度的单元测试入手进行分析：

@Test
public void testDelayScheduling() {
  FSLeafQueue queue = Mockito.mock(FSLeafQueue.class);
  Priority prio = Mockito.mock(Priority.class);
  Mockito.when(prio.getPriority()).thenReturn(1);
  double nodeLocalityThreshold = .5;
  double rackLocalityThreshold = .6;

  ApplicationAttemptId applicationAttemptId = createAppAttemptId(1, 1);
  RMContext rmContext = resourceManager.getRMContext();
  FSAppAttempt schedulerApp =
      new FSAppAttempt(scheduler, applicationAttemptId, "user1", queue ,
          null, rmContext);

  // Default level should be node-local
  assertEquals(NodeType.NODE_LOCAL, schedulerApp.getAllowedLocalityLevel(
      prio, 10, nodeLocalityThreshold, rackLocalityThreshold));

  // First five scheduling opportunities should remain node local
  for (int i = 0; i < 5; i++) {
   
    schedulerApp.addSchedulingOpportunity(prio);
    assertEquals(NodeType.NODE_LOCAL, schedulerApp.getAllowedLocalityLevel(
        prio, 10, nodeLocalityThreshold, rackLocalityThreshold));
  }

  // After five it should switch to rack local
  schedulerApp.addSchedulingOpportunity(prio);
  assertEquals(NodeType.RACK_LOCAL, schedulerApp.getAllowedLocalityLevel(
      prio, 10, nodeLocalityThreshold, rackLocalityThreshold));

  // Manually set back to node local
  schedulerApp.resetAllowedLocalityLevel(prio, NodeType.NODE_LOCAL);
  schedulerApp.resetSchedulingOpportunities(prio);
  assertEquals(NodeType.NODE_LOCAL, schedulerApp.getAllowedLocalityLevel(
      prio, 10, nodeLocalityThreshold, rackLocalityThreshold));

  // Now escalate again to rack-local, then to off-switch
  for (int i = 0; i < 5; i++) {
   
    schedulerApp.addSchedulingOpportunity(prio);
    assertEquals(NodeType.NODE_LOCAL, schedulerApp.getAllowedLocalityLevel(
        prio, 10, nodeLocalityThreshold, rackLocalityThreshold));
  }

  schedulerApp.addSchedulingOpportunity(prio);
  assertEquals(NodeType.RACK_LOCAL, schedulerApp.getAllowedLocalityLevel(
      prio, 10, nodeLocalityThreshold, rackLocalityThreshold));

  for (int i = 0; i < 6; i++) {
   
    schedulerApp.addSchedulingOpportunity(prio);
    assertEquals(NodeType.RACK_LOCAL, schedulerApp.getAllowedLocalityLevel(
        prio, 10, nodeLocalityThreshold, rackLocalityThreshold));
  }

  schedulerApp.addSchedulingOpportunity(prio);
  assertEquals(NodeType.OFF_SWITCH, schedulerApp.getAllowedLocalityLevel(
      prio, 10, nodeLocalityThreshold, rackLocalityThreshold));
}

我们从自带的单元测试入手：
这两个参数分别设置为了 0.5 和 0.6
double nodeLocalityThreshold = .5;
double rackLocalityThreshold = .6;

schedulerApp.getAllowedLocalityLevel（）:
来看一下这个方法：

public synchronized NodeType getAllowedLocalityLevel(Priority priority,
    int numNodes, double nodeLocalityThreshold, double rackLocalityThreshold) {
  // upper limit on threshold
  if (nodeLocalityThreshold > 1.0) { nodeLocalityThreshold = 1.0; }
  if (rackLocalityThreshold > 1.0) { rackLocalityThreshold = 1.0; }

  // If delay scheduling is not being used, can schedule anywhere
  if (nodeLocalityThreshold < 0.0 || rackLocalityThreshold < 0.0) {
    return NodeType.OFF_SWITCH;
  }

  // Default level is NODE_LOCAL
  if (!allowedLocalityLevel.containsKey(priority)) {
    allowedL