[TEZ-356] In TaskScheduler#releaseUnassignedContainers, containers haven't really been put into releasedContainers

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2.0
• Fix Version/s: 0.2.0
• Assignee: Siddharth Seth
• Reporter: joeyli
• Created: 12/Aug/13 07:59
• Updated: 01/Dec/13 20:21
• Resolved: 19/Aug/13 17:09

Description

  private void releaseUnassignedContainers(List<Container> containers) {
    for (Container container : containers) {
      releaseContainer(container.getId(), null);
      LOG.info("No RM requests matching container: " + container);
    }
  }

  private void releaseContainer(ContainerId containerId, Object task) {
    amRmClient.releaseAssignedContainer(containerId);
    if(task != null) {
      releasedContainers.put(containerId, task);
    }
  }

Issue Links

• is part of: TEZ-344 Support delayed scheduling for re-used containers