[
https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-378:
-----------------------------
Attachment: YARN-378_7.patch
I've split the previous patch into two parts. This one is mainly based on
YARN-378_4.patch. Additionally, I've addressed the following issues:
1. Adding mapreduce.am.max-attempts and the default value to mapred-default.xml
2. Expanding the documentation in mapred-default.xml and yarn-default.xml
3. Removing the reference of RMAppImpl in ApplicationSubmissionContext
4. Renaming max retries to max app attempts in all related places, and adding
prefix "individual" and "global" for the number of application-specific and
system-wide number respectively
5. Removing the check of global maxAppAttempts
> 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
> Attachments: YARN-378_1.patch, YARN-378_2.patch, YARN-378_3.patch,
> YARN-378_4.patch, YARN-378_5.patch, YARN-378_6.patch, YARN-378_6.patch,
> YARN-378_7.patch
>
>
> 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
