You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2013/03/05 01:01:15 UTC
[jira] [Commented] (YARN-378) ApplicationMaster retry times should
be set by Client
[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592824#comment-13592824 ]
Zhijie Shen commented on YARN-378:
----------------------------------
My strategy is that:
1. Create another Yarn property "yarn.application.am.max-retries", which is the name of the application-specific max retry number (no default value is required).
2. The number is passed from client to resourcemanager (set by the client and imbedded in job.xml).
3. If "yarn.application.am.max-retries" is not set, the value of "yarn.resourcemanager.am.max-retries" is used. Otherwise, if "yarn.application.am.max-retries" <= "yarn.resourcemanager.am.max-retries", the value of "yarn.application.am.max-retries" is used. In the remaining case, the value of "yarn.resourcemanager.am.max-retries" is used and a warning record is logged.
How do you think abou the strategy?
> ApplicationMaster retry times should be set by Client
> -----------------------------------------------------
>
> Key: YARN-378
> URL: https://issues.apache.org/jira/browse/YARN-378
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: client, resourcemanager
> Environment: suse
> Reporter: xieguiming
> Assignee: Zhijie Shen
> Labels: usability
>
> We should support that different client or user have different ApplicationMaster retry times. It also say that "yarn.resourcemanager.am.max-retries" should be set by client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira