[
https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602055#comment-13602055
]
Vinod Kumar Vavilapalli commented on YARN-378:
----------------------------------------------
+1 for maxAppAttempts naming.
+1 to Bobby's proposal to add it to env. We are sending across other important
things like app-attempt-id as part of the env, so +1 for adding this info too.
bq. First in some init method that reads the global value from config, checks
for errors and sets a sensible default global value.
Yes, this should happen somewhere in the main thread and crash the RM in case
of invalid configs. RMApp gets created much later, so..
bq. Env vars are brittle..
I suppose this is on Windows?
> 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
>
>
> 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
