[
https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649664#comment-14649664
]
Steve Loughran commented on YARN-3998:
--------------------------------------
Do it at the app level and you get notification of what is going on, e.g. you
can track failure count and decide how to react.
but whenever a launch fails, you have to go through the queue of requesting a
new container & relocalising. Having a small sleep & retry would skip all that
and possibly increase the chance of a container coming up: provided that launch
failure was due to some transient condition on the specific host which failed
to launch.
Jun: what issue is storm/YARN suffering from that's triggering this unreliable
startup?
> Add retry-times to let NM re-launch container when it fails to run
> ------------------------------------------------------------------
>
> Key: YARN-3998
> URL: https://issues.apache.org/jira/browse/YARN-3998
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Jun Gong
> Assignee: Jun Gong
>
> I'd like to add a field(retry-times) in ContainerLaunchContext. When AM
> launches containers, it could specify the value. Then NM will re-launch the
> container 'retry-times' times when it fails to run(e.g.exit code is not 0).
> It will save a lot of time. It avoids container localization. RM does not
> need to re-schedule the container. And local files in container's working
> directory will be left for re-use.(If container have downloaded some big
> files, it does not need to re-download them when running again.)
> We find it is useful in systems like Storm.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
