[
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_5.patch
In the newest patch, I've addressed @Robert's comments, which is setting
numMaxRetries when composing the ApplicationSubmissionContext, and adding the
property name into mapred-default.xml.
In addition, I've modified AMRMProtocol to enable AM to get numMaxRetries from
RM. The number is obtained when AM gets registered on RM. Previously,
isLastAMRetry was computed in init(). Now, since the number is not available
until AM is registered, I postponed the computation until it need to be used.
One place in the patch that I'm not quite happy with is that I had to add
additional member variable and getter for ContainerAllocator to allow AM to
read numMaxRetries. Please have a look at patch. Your comments are appreciated.
> 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
>
>
> 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
