[
https://issues.apache.org/jira/browse/YARN-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904028#comment-14904028
]
Weiwei Yang commented on YARN-4165:
-----------------------------------
Hello Jason
Thanks for looking this. I checked YARN 957 but I think this is a different
problem.
I have 3 nodes
NM1 8G
NM2 8G
NM3 8G
I submitted an application, requires 4 containers and each of them relative big
memory like 5G, its app master requires 1G, so RM fills 3 containers and 1 app
master but leaving 1 outstanding request, *unexpectedly* RM reserved 1
container on all 3 nodes like
NM1 - 1 container, 1 app master - 6G used - 2G left - 5G reserved
NM2 - 1 container - 5G used - 3G left - 5G reserved
NM3 - 1 container - 5G used - 3G left - 5G reserved
I am not sure yet why we run into such situation, but it might be related to
YARN-1769, I am still investigating, if you have any pointers or comments,
please let me know. Thanks.
> 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: capacity scheduler, 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)
