[
https://issues.apache.org/jira/browse/YARN-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459242#comment-15459242
]
Jason Lowe commented on YARN-5617:
----------------------------------
See TEZ-3426 for an example of an app framework that was depending upon
maxattempts=1 really meaning at most one attempt. I suspect there are other
cases where app frameworks are not properly prepared to run more than one
attempt correctly and those frameworks or their users are setting max app
attempts=1 to avoid the issues. After YARN-614 that won't always be the case.
Filing this ticket in case we want to consider interpreting maxattempts=1 as a
special-case.
> AMs only intended to run one attempt can be run more than once
> --------------------------------------------------------------
>
> Key: YARN-5617
> URL: https://issues.apache.org/jira/browse/YARN-5617
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.5.0
> Reporter: Jason Lowe
>
> There are times when a user only wants to run an application with one
> attempt. Examples would be cases where the second AM attempt is not prepared
> to handle recovery or will accidentally corrupt state (e.g.: by re-executing
> something from scratch that should not be). Prior to YARN-614 setting the
> max attempts to 1 would guarantee the app ran at most one attempt, but now it
> can run more than one attempt if the attempts fail due to a fault not
> attributed to the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
