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 00:01:15 GMT

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

Zhijie Shen commented on YARN-378:

My strategy is that:

1. Create another Yarn property "yarn.application.am.max-retries", which is the name of the
application-specific max retry number (no default value is required).

2. The number is passed from client to resourcemanager (set by the client and imbedded in

3. If "yarn.application.am.max-retries" is not set, the value of "yarn.resourcemanager.am.max-retries"
is used. Otherwise, if "yarn.application.am.max-retries" <= "yarn.resourcemanager.am.max-retries",
the value of "yarn.application.am.max-retries" is used. In the remaining case, the value of
"yarn.resourcemanager.am.max-retries" is used and a warning record is logged.

How do you think abou the strategy?
> 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