hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit
Date Tue, 03 Feb 2015 20:50:36 GMT

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

Allen Wittenauer commented on YARN-3119:
----------------------------------------

"Snow leopards already have poachers so it's ok if I kill this one."

I think the only way this would be acceptable is if two things happen:

a) It is configurable to turn this functionality off.
b) The setting in the yarn-default.xml file came with a big warning saying that it may lead
to system instability and/or unpredictability.

> Memory limit check need not be enforced unless aggregate usage of all containers is near
limit
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-3119
>                 URL: https://issues.apache.org/jira/browse/YARN-3119
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-3119.prelim.patch
>
>
> Today we kill any container preemptively even if the total usage of containers for that
is well within the limit for YARN. Instead if we enforce memory limit only if the total limit
of all containers is close to some configurable ratio of overall memory assigned to containers,
we can allow for flexibility in container memory usage without adverse effects. This is similar
in principle to how cgroups uses soft_limit_in_bytes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message