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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/11/01 12:12:34 UTC
[jira] [Created] (YARN-2793) YARN service containers to support
different memory limit policies
Steve Loughran created YARN-2793:
------------------------------------
Summary: YARN service containers to support different memory limit policies
Key: YARN-2793
URL: https://issues.apache.org/jira/browse/YARN-2793
Project: Hadoop YARN
Issue Type: Sub-task
Components: nodemanager
Reporter: Steve Loughran
Service containers may have different memory policies from applications. Specifically, it may be more important to keep the container running if its memory goes over allocated, rather than killing it.
If the memory over-use could be detected, the AM could then make an attempt to request more resources for that container, so increasing its allocation. And, if that fails, shutting down the node cleanly. As it is, a killed container looks like a failure to the AM, which runs the risk of concluding that the app and/or host is in trouble, when it is merely the memory requirement is too low
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)