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

Hudson commented on YARN-5117:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #9881 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/9881/])
YARN-5117. QueuingContainerManager does not start GUARANTEED Container (arun 
suresh: rev 4fc09a897b25914a9b9321cc443f3f3ff3d776d5)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/queuing/QueuingContainerManagerImpl.java
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/queuing/TestQueuingContainerManager.java
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/monitor/ContainersMonitorImpl.java


> 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
>
>         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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to