Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 14 Mar 2013 08:28:14 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12550672.1334234324274.439686.1363249694798@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=13602139#comment-13602139 ] 

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

{quote}
Env vars are brittle..
{quote}

Does the env method work with other applications? I can see the merit of embedding maxAppAttempts into AM registration response is that the number can be read by AM of other applications in the same way. I think we can begin to discuss the issue related to informing AM of maxAppAttempts in MAPREDUCE-5062.
                
> 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, YARN-378_7.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