[jira] [Resolved] (TEZ-588) TaskScheduler may end up releasing containers and getting stuck without enough resources

["Bikas Saha (JIRA)" <ji...@apache.org>]

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

Bikas Saha resolved TEZ-588.
----------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0
         Assignee: Bikas Saha

commit ae541f78de02fb7418ae2955bf8da9557e9901c6
Author: Bikas Saha <bi...@apache.org>
Date:   Fri Nov 8 00:28:03 2013 -0800

    TEZ-588. TaskScheduler may end up releasing containers and getting stuck without enough resources (bikas)

> TaskScheduler may end up releasing containers and getting stuck without enough resources
> ----------------------------------------------------------------------------------------
>
>                 Key: TEZ-588
>                 URL: https://issues.apache.org/jira/browse/TEZ-588
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>             Fix For: 0.2.0
>
>         Attachments: TEZ-588.1.patch
>
>
> {code}
> if (hitFinalMatchLevel) {
>             // Are there any pending requests at any priority?
>             // release if there are tasks or this is not a session
>             if (!taskRequests.isEmpty() || !appContext.isSession()) {
>               LOG.info("Releasing held container as either there are pending but "
>                 + " unmatched requests or this is not a session"
>                 + ", containerId=" + heldContainer.container.getId()
>                 + ", pendingTasks=" + !taskRequests.isEmpty()
>                 + ", isSession=" + appContext.isSession()
>                 + ". isNew=" + isNew);
>               releaseUnassignedContainers(
>                 Lists.newArrayList(heldContainer.container));
>             }
> {code}
> The above code releases these containers and expects to get better matching containers from the RM. But when the RM first allocated these containers to the job then it had already reduced the ask for this job. If the ask on the RM is currently 0 then these released containers will not be replaced by the RM with new containers until the the AM makes new container requests for the tasks that it has not yet been able to match to these containers. We dont seem to be making those new container requests and thus risk getting stuck on resources.



--
This message was sent by Atlassian JIRA
(v6.1#6144)