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:07:47 UTC

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

    [ https://issues.apache.org/jira/browse/TEZ-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736677#comment-13736677 ] 

joeyli commented on TEZ-356:
----------------------------

[#Hitesh Shah] [#Bikas Saha] [#Siddharth Seth] How do we fix it?
let null put into releasedContainers, or use a dummy object in releaseUnassignedContainers? 
                
> 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