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 19:36:14 GMT

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

Zhijie Shen commented on YARN-378:

Sorry, it's a typo in my previous comment. In fact, I wanted to say "-Dyarn.application.am.max-retries".

I'd like to "yarn.application.am.max-retries" as the name of the application-specific configuration.
IMHO, "mapreduce.am.max-retries" will not be suitable if the submitted application is not
a mapreduce job. Since Yarn is eventually a management system of various computation frameworks
(e.g. Apache Giraph). I'd rather have the configuration name to be independent of mapreduce,
as it is not only for mapreduce.

However, if the "yarn" prefix is confusing, how do you think about "application.am.max-retries"?
> 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