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

Hudson commented on YARN-542:
-----------------------------

Integrated in Hadoop-trunk-Commit #3642 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/3642/])
    YARN-542. Changed the default global AM max-attempts value to be not one. 
Contributed by Zhijie Shen. (Revision 1470094)

     Result = SUCCESS
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1470094
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMRestart.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/TestRMAppTransitions.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebServicesApps.java

                
> Change the default global AM max-attempts value to be not one
> -------------------------------------------------------------
>
>                 Key: YARN-542
>                 URL: https://issues.apache.org/jira/browse/YARN-542
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Zhijie Shen
>             Fix For: 2.0.5-beta
>
>         Attachments: YARN-542.1.patch
>
>
> Today, the global AM max-attempts is set to 1 which is a bad choice. AM 
> max-attempts accounts for both AM level failures as well as container crashes 
> due to localization issue, lost nodes etc. To account for AM crashes due to 
> problems that are not caused by user code, mainly lost nodes, we want to give 
> AMs some retires.
> I propose we change it to atleast two. Can change it to 4 to match other 
> retry-configs.

--
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

Reply via email to