hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5773) RM recovery too slow due to LeafQueue#activateApplication()
Date Wed, 26 Oct 2016 18:08:00 GMT

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

Varun Saxena commented on YARN-5773:

bq. Now the question here is to invoke activateApplications after scheduler recovery is done.
Do we need to activateApplications ? Applications would be activated when node re-registers.
Right ?

Coming to code in the patch, checking against cluster resource being 0 should be fine but
resources may not be 0 only on recovery so should we update AM diagnostics if we return right
from beginning of activateApplications ? Also a log should be added.
One more thing, the indication of whether attempt is recovering or not can be received from
SchedulerApplicationAttempt#isRecovering which is filled from AppAttemptAddedSchedulerEvent.
This can be used as well to differentiate between 0 resources because app is recovering or
no nodes registered.

Also, in the patch LOG.debug statements should be guarded with LOG.isDebugEnabled check

> 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
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>            Priority: Critical
>         Attachments: YARN-5773.0001.patch, YARN-5773.0002.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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message