[ https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291523#comment-14291523 ]
Hadoop QA commented on YARN-3094: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12694477/YARN-3094.2.patch against trunk revision 7b82c4a. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6415//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6415//console This message is automatically generated. > reset timer for liveness monitors after RM recovery > --------------------------------------------------- > > Key: YARN-3094 > URL: https://issues.apache.org/jira/browse/YARN-3094 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.6.0 > Reporter: Jun Gong > Assignee: Jun Gong > Attachments: YARN-3094.2.patch, YARN-3094.patch > > > When RM restarts, it will recover RMAppAttempts and registry them to > AMLivenessMonitor if they are not in final state. AM will time out in RM if > the recover process takes long time due to some reasons(e.g. too many apps). > In our system, we found the recover process took about 3 mins, and all AM > time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)