Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 13 Mar 2013 21:58:13 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12550672.1334234324274.437156.1363211893441@arcas>
In-Reply-To: <JIRA.12550672.1334234324274@arcas>
References: <JIRA.12550672.1334234324274@arcas>
Subject: [jira] [Commented] (YARN-378) ApplicationMaster retry times should
 be set by Client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zhijie Shen commented on YARN-378:
----------------------------------

@Robert, if RM is supposed to inform AM about the number, it seems to happen no early than AM registration. Otherwise, is the launch environment of the AM container possible to set by RM? Such that AM can got the number when it is constructed?

@Bikas, I like maxAppAttempts better, and the computation logic doesn't need to be changed (i.e., otherwise, retries + 1).
                
> 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