You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "joeyli (JIRA)" <ji...@apache.org> on 2013/08/12 10:00:54 UTC

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

joeyli created TEZ-356:
--------------------------

             Summary: In TaskScheduler#releaseUnassignedContainers,  containers haven't really been put into releasedContainers
                 Key: TEZ-356
                 URL: https://issues.apache.org/jira/browse/TEZ-356
             Project: Apache Tez
          Issue Type: Bug
    Affects Versions: 0.2.0
            Reporter: joeyli
             Fix For: 0.2.0


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

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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira