hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kyungwan nam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7408) total capacity could be occupied by a large container request
Date Mon, 30 Oct 2017 09:22:00 GMT

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

kyungwan nam commented on YARN-7408:
------------------------------------

Hi [~jlowe].
Thank you for your comment and suggestion!
I have a question.

{quote}
Proposals to artificially limit reservations for an app also risk this same indefinite postponement
if the scheduler happened to choose poorly where to place the limited number of reservations
{quote}

if reservation-continue-looking is enabled, does it try to allocate on another nodes within
the limited number of reservations?


> total capacity could be occupied by a large container request
> -------------------------------------------------------------
>
>                 Key: YARN-7408
>                 URL: https://issues.apache.org/jira/browse/YARN-7408
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: kyungwan nam
>
> if NM can not afford to allocate a large container request, it will be reserved container.
> but, in a cluster with long running apps, it is not often that running containers are
released.
> in cases like this, reserved containers will be increased as time goes on. as a result,
total capacity could be occupied by reserved resources.
> it makes other container requests starve.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message