[
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_8.patch
Make the patch be restricted in the scope of YARN only. In addition,
maxAppRetries is set in the environment when launching AM. The global
maxAppRetries is validated when RM is initiated, if it is non-positive, RM will
crash. Note that MRAppMaster and TestStagingCleanup have reference to
YarnConfiguration.RM_AM_MAX_RETRIES, which has been changed to
YarnConfiguration.RM_AM_MAX_ATTEMPTS. Therefore, the build of mapreduce will be
broken temporally.
> 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, YARN-378_8.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
