[
https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832068#comment-15832068
]
Eric Payne commented on YARN-5889:
----------------------------------
bq. it never gets above {{queue-capacity * MULP}}
[~sunilg] and [~leftnoteasy], although this statement is true and I correctly
stated the symptoms, I misdiagnosed the root cause in my [comments
above|https://issues.apache.org/jira/secure/EditComment!default.jspa?id=13021186&commentId=15829005].
Sorry for the confusion.
It appears that the root cause is that {{UM#User#assignContainer}} is not
incrementing {{TotalResUsedByActiveUsers}} for the AM. The first time through
{{assignContainer}} for a new app, the user isn't active yet, so the used
resources count is not incremented. Consequently,
{{resource-used-by-active-users}} is always smaller than the actual value, and
never gets bigger than {{queue-capacity * MULP}}:
{code: title=UsersManager#computeUserLimit}
active-user-limit = max(
resource-used-by-active-users / #active-users,
queue-capacity * MULP
)
{code}
[~sunilg], do we need the {{isAnActiveUser}} checks in {{assignContainer}} and
{{releaseContainer}}? I removed these checks in my local build and the
application is able to use all of the queue and cluster.
> 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: [email protected]
For additional commands, e-mail: [email protected]
