[ https://issues.apache.org/jira/browse/YARN-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616557#comment-15616557 ]
Varun Saxena commented on YARN-5773: ------------------------------------ Thanks [~bibinchundatt] for the patch. Changes look fine to me. Will commit it pending Jenkins. There are a couple of typos though in the log message below. Will take care while committing. {code} 836 LOG.info("Skiping activateApplications for " 837 + application.getApplicationAttemptId() 838 + " since cluster resorce is " + Resources.none()); {code} > RM recovery too slow due to LeafQueue#activateApplication() > ----------------------------------------------------------- > > Key: YARN-5773 > URL: https://issues.apache.org/jira/browse/YARN-5773 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler, rolling upgrade > Reporter: Bibin A Chundatt > Assignee: Bibin A Chundatt > Priority: Critical > Labels: oct16-medium > Attachments: YARN-5773.0001.patch, YARN-5773.0002.patch, > YARN-5773.0004.patch, YARN-5773.0005.patch, YARN-5773.0006.patch, > YARN-5773.0007.patch, YARN-5773.003.patch > > > # Submit application 10K application to default queue. > # All applications are in accepted state > # Now restart resourcemanager > For each application recovery {{LeafQueue#activateApplications()}} is > invoked.Resulting in AM limit check to be done even before Node managers are > getting registered. > Total iteration for N application is about {{N(N+1)/2}} for {{10K}} > application {{50000000}} iterations causing time take for Rm to be active > more than 10 min. > Since NM resources are not yet added to during recovery we should skip > {{activateApplicaiton()}} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org