You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "kyungwan nam (JIRA)" <ji...@apache.org> on 2017/10/27 08:44:00 UTC
[jira] [Commented] (YARN-7408) total capacity could be occupied by
a large container request
[ https://issues.apache.org/jira/browse/YARN-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221953#comment-16221953 ]
kyungwan nam commented on YARN-7408:
------------------------------------
Currently, the number of reserved containers for an application is increased proportionally according to how long it starves.
What about limiting maximum reserved resource, which an application can take.
Does this approach make sense? please correct me know if I am wrong.
Any comments or suggestions are welcome.
> 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