tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEZ-356) In TaskScheduler#releaseUnassignedContainers, containers haven't really been put into releasedContainers
Date Mon, 19 Aug 2013 17:09:48 GMT

     [ https://issues.apache.org/jira/browse/TEZ-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siddharth Seth resolved TEZ-356.
--------------------------------

    Resolution: Fixed

Fixed as part of TEZ-344.
                
> 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
>            Assignee: Siddharth Seth
>             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

Mime
View raw message