[
https://issues.apache.org/jira/browse/YARN-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939658#comment-13939658
]
Krisztian Horvath commented on YARN-1842:
-----------------------------------------
The original exception occurred on osx with hadoop 2.3.0, but after trying on
debian with hadoop 2.2.0 the result is the same. I attached some logs.
The Flume agent starts with a provider creating the shell command to exec.
Other than that, the application should run in the requested container, right?
Because it seems that it is running outside of it (setting the yarn.memory to
8mb and the jvm heap size of the application a much larger and works fine).
> 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)
