hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MENG DING (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4165) An outstanding container request makes all nodes to be reserved causing all jobs pending
Date Wed, 23 Sep 2015 14:36:04 GMT

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

MENG DING commented on YARN-4165:
---------------------------------

I think this is expected behavior according to the current scheduling logic. Assuming resource
usage of the app has not gone over user/queue limit, then because of the starvation of the
application, the scheduler will keep reserving containers for unsatisfied requests.

> 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)

Mime
View raw message