[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602716#comment-13602716 ]
Hadoop QA commented on YARN-378: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12573761/YARN-378_8.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 7 new or modified test files. {color:green}+1 tests included appear to have a timeout.{color} {color:red}-1 javac{color:red}. The patch appears to cause the build to fail. Console output: https://builds.apache.org/job/PreCommit-YARN-Build/515//console This message is automatically generated. > 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, YARN-378_8.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