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

Weiwei Yang commented on YARN-4165:
-----------------------------------

Hi Jason 

We are using capacity scheduler, and the problem can be described as, we have 2 
nodes, AAAA and BBBB. If there is an outstanding container request for APP1, 
both AAAA and BBBB is reserved for the application, RM log looks like

2015-09-21 20:39:07,990 INFO  capacity.CapacityScheduler 
(CapacityScheduler.java:allocateContainersToNode(1240)) - Skipping scheduling 
since node AAAA:45454 is reserved by application 
appattempt_1442889801665_0001_000001
2015-09-21 20:40:10,990 INFO  capacity.CapacityScheduler 
(CapacityScheduler.java:allocateContainersToNode(1240)) - Skipping scheduling 
since node BBBB:45454 is reserved by application 
appattempt_1442889801665_0001_000001

then when I submit a new job APP2, the app master cannot be allocated because 
all nodes are reserved.

> An outstanding container request makes all nodes to be reserved causing all 
> jobs pending
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-4165
>                 URL: https://issues.apache.org/jira/browse/YARN-4165
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager, scheduler
>    Affects Versions: 2.7.1
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>
> We have a long running service in YARN, it has a outstanding container 
> request that YARN cannot satisfy (require more memory that nodemanager can 
> supply). Then YARN reserves all nodes for this application, when I submit 
> other jobs (require relative small memory that nodemanager can supply), all 
> jobs are pending because YARN skips scheduling containers on the nodes that 
> have been reserved.



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

Reply via email to