hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client
Date Thu, 14 Mar 2013 15:24:13 GMT

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

Robert Joseph Evans commented on YARN-378:

Looking at the code too I am fine with renaming retries to attempts.  But we need to mark
this JIRA as an incompatible change or put in a deprecated config mapping.  We are early enough
in YARN that deprecating it seems like a waste.
> 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

View raw message