[jira] [Assigned] (YARN-1076) RM gets stuck with a reservation, ignoring new containers

["Omkar Vinit Joshi (JIRA)" <ji...@apache.org>]

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

Omkar Vinit Joshi reassigned YARN-1076:
---------------------------------------

    Assignee: Omkar Vinit Joshi
    
> RM gets stuck with a reservation, ignoring new containers
> ---------------------------------------------------------
>
>                 Key: YARN-1076
>                 URL: https://issues.apache.org/jira/browse/YARN-1076
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Maysam Yabandeh
>            Assignee: Omkar Vinit Joshi
>            Priority: Minor
>         Attachments: YARN-1076.patch
>
>
> LeafQueue#assignToQueue rejects newly available containers if potentialNewCapacity > absoluteMaxCapacity:
> {code:java}
>   private synchronized boolean assignToQueue(Resource clusterResource, 
>       Resource required) {
>     // Check how of the cluster's absolute capacity we are currently using...
>     float potentialNewCapacity = 
>         Resources.divide(
>             resourceCalculator, clusterResource, 
>             Resources.add(usedResources, required), 
>             clusterResource);
>     if (potentialNewCapacity > absoluteMaxCapacity) {
>       //... 
>       return false;
>     }
>     return true;
>   }
> {code}
> The usedResources, which is used to computed potentialNewCapacity, is composed of both actual and reserved containers. So, a prior reservation could causes RM to reject newly available containers, despite the starvation report.

--
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