hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5117) QueuingContainerManager does not start GUARANTEED Container even if Resources are available
Date Mon, 13 Nov 2017 23:10:00 GMT

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

Andrew Wang updated YARN-5117:
------------------------------
    Fix Version/s:     (was: 3.0.0)
                   3.0.0-alpha1

> 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: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Konstantinos Karanasos
>             Fix For: 2.9.0, 3.0.0-alpha1
>
>         Attachments: YARN-5117.001.patch, YARN-5117.002.patch, YARN-5117.003.patch, YARN-5117.004.patch
>
>
> 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.4.14#64029)

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


Mime
View raw message