[
https://issues.apache.org/jira/browse/YARN-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904878#comment-14904878
]
Wangda Tan commented on YARN-4165:
----------------------------------
I think this is not expected behavior, we shouldn't consider one application is
starving if it reserved #containers as same as pending #containers.
[~cheersyang], could you write a test about this? It will be easier to identify
this issue if we have a unit test to prove it.
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)
