hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client
Date Tue, 05 Mar 2013 17:12:14 GMT

    [ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593599#comment-13593599

Zhijie Shen commented on YARN-378:

Thanks, Robert! I"ve also realized that RM cannot read job.xml. There're two places where
max-retries are used. One is in MRAppMaster and the other in RMAppImpl. In the first place,
AM can read job.xml directly to get the application-specific configuration. In the second
place, RM has to get the setting through ApplicationSubmissionContext, such that I add the
setter/getter for NumMaxRetries.

The MR client can either use -Dyarn.resourcemanager.am.max-retries or parse mapred-site.xml
to get the configuration, and set it in ApplicationSubmissionContext.
> 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

View raw message