You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2016/05/20 08:57:13 UTC

[jira] [Commented] (YARN-5117) QueuingContainerManager does not start GUARANTEED Container even if Resources are available

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

Arun Suresh commented on YARN-5117:
-----------------------------------

The {{ContainersMonitorImpl::hasResourcesAvailable()}} function performs the following check :
{noformat}
    if (this.containersAllocation.getCPU()
          + allocatedCpuUsage(pti) > 1.0f) {
        return false;
      }
{noformat}

It looks like the condition is always true. I guess instead of 1.0f it should be total number of available cores ?

> QueuingContainerManager does not start GUARANTEED Container even if Resources are available
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-5117
>                 URL: https://issues.apache.org/jira/browse/YARN-5117
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Konstantinos Karanasos
>
> When NM Queuing is turned on, it looks like GUARANTEED containers do not start even when there are no containers running on the NM. The following is seen in the logs :
> {noformat}
> .....
> 2016-05-19 22:34:12,711 INFO  [IPC Server handler 0 on 49809] queuing.QueuingContainerManagerImpl (QueuingContainerManagerImpl.java:pickOpportunisticContainersToKill(351)) - There are no sufficient resources to start guaranteed container_1463711648301_0001_01_000001 even after attempting to kill any running opportunistic containers.
> .....
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org