[
https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836712#comment-15836712
]
Eric Payne commented on YARN-5889:
----------------------------------
bq. LQ#allocateResource will invoke UM#User#assignContainer. So all containers
including AM will hit here.
[~sunilg], I'm sorry I wasn't clear.
As you say, {{UM#User#assignContainer}} is called for the AM. However, since
{{userName}} is not active at that point, {{incUsed}} is not called and the
AM's resources are not incremented:
{code}
if (activeUsersManager.isAnActiveUser(userName)) {
activeUsersManager.getTotalResUsedByActiveUsers().incUsed(nodePartition,
resource);
}
{code}
> Improve user-limit calculation in capacity scheduler
> ----------------------------------------------------
>
> Key: YARN-5889
> URL: https://issues.apache.org/jira/browse/YARN-5889
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: YARN-5889.0001.patch,
> YARN-5889.0001.suggested.patchnotes, YARN-5889.0002.patch,
> YARN-5889.0003.patch, YARN-5889.0004.patch, YARN-5889.0005.patch,
> YARN-5889.v0.patch, YARN-5889.v1.patch, YARN-5889.v2.patch
>
>
> Currently user-limit is computed during every heartbeat allocation cycle with
> a write lock. To improve performance, this tickets is focussing on moving
> user-limit calculation out of heartbeat allocation flow.
--
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
