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 "Konstantinos Karanasos (JIRA)" <ji...@apache.org> on 2016/05/21 02:04:12 UTC
[jira] [Updated] (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:all-tabpanel ]
Konstantinos Karanasos updated YARN-5117:
-----------------------------------------
Attachment: YARN-5117.001.patch
Attaching patch. I changed the way we are calculating the allocated CPU usage of a given ProcessTreeInfo. Returned value is still normalized between 0.0 and 1.0.
> 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
> Attachments: YARN-5117.001.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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org