[
https://issues.apache.org/jira/browse/YARN-5773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612297#comment-15612297
]
Bibin A Chundatt edited comment on YARN-5773 at 10/27/16 3:52 PM:
------------------------------------------------------------------
{quote}
When cluster resource is 0, this is unlikely to be a case.
{quote}
I did verify the same when cluster resource is empty and submit application.The
first application attempt is activated.
I think its should be fine keeping the same. Since the loop will run only
once.Hope in last patch no changes are required.
was (Author: bibinchundatt):
{quote}
When cluster resource is 0, this is unlikely to be a case.
{quote}
I did verify the same when cluster resource is empty and submit application.The
first application attempt is activated.
I think its should be fine keeping the same. Since the loop will run one once.
> 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.0004.patch, YARN-5773.0005.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: [email protected]
For additional commands, e-mail: [email protected]
