[
https://issues.apache.org/jira/browse/YARN-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939720#comment-13939720
]
Steve Loughran commented on YARN-1842:
--------------------------------------
-even if you start up a process with lots of RAM, it still runs in a container
unless you tell YARN to enforce memory limits:
{code}
<property>
<description>Whether physical memory limits will be enforced for
containers.
</description>
<name>yarn.nodemanager.pmem-check-enabled</name>
<value>true</value>
</property>
<property>
<name>yarn.nodemanager.vmem-check-enabled</name>
<value>true</value>
</property>
{code}
> InvalidApplicationMasterRequestException raised during AM-requested shutdown
> ----------------------------------------------------------------------------
>
> Key: YARN-1842
> URL: https://issues.apache.org/jira/browse/YARN-1842
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: hoyalogs.tar.gz
>
>
> Report of the RM raising a stack trace
> [https://gist.github.com/matyix/9596735] during AM-initiated shutdown. The AM
> could just swallow this and exit, but it could be a sign of a race condition
> YARN-side, or maybe just in the RM client code/AM dual signalling the
> shutdown.
> I haven't replicated this myself; maybe the stack will help track down the
> problem. Otherwise: what is the policy YARN apps should adopt for AM's
> handling errors on shutdown? go straight to an exit(-1)?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
