[
https://issues.apache.org/jira/browse/YARN-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981474#comment-13981474
]
Oleg Zhurakousky commented on YARN-1985:
----------------------------------------
Actually a bit of a good news. The other two containers didn't start because
one of my nodes had its date/time messed up resulting
{code}
org.apache.hadoop.yarn.exceptions.YarnException: Unauthorized request to start
container.
This token is expired. current time is 1398449721411 found 1398448925681
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
. . .
{code}
So handling 'onStartContainerError' event would do.
So this makes it much less of an issue and I can work around it (actually
already did), but the fact that _ExitStatus_ for the containers that did start
was 0 is still a problem.
Downgrading it to minor
> YARN issues wrong state when "running beyond virtual memory limits"
> -------------------------------------------------------------------
>
> Key: YARN-1985
> URL: https://issues.apache.org/jira/browse/YARN-1985
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: Oleg Zhurakousky
> Priority: Minor
>
> When deploying YARN application with multiple containers and AM determines
> that the resource limits been reached (e.g., virtual memory) it starts
> killing *all* containers while reporting a *single* COMPLETED status
> essentially hanging AM waiting for more containers to report its state.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
