[
https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829005#comment-15829005
]
Eric Payne commented on YARN-5889:
----------------------------------
[~leftnoteasy] and [~sunilg], I'm sorry for coming back to this point, but I
just now realized the full consequences.
{code: title=UsersManager#computeUserLimit}
active-user-limit = max(
resource-used-by-active-users / #active-users,
queue-capacity * MULP
)
{code}
With the above algorithm, {{active-user-limit}} never goes above
{{resource-used-by-active-users / #active-users}} if MULP is less than 100%. I
think this is because {{consumed}} is never greater than {{queue-capacity}} in
that case.
That is to say:
- {{queue-capacity}} = {{partitionResource * queueAbsCapPerPartition}}
- {{queue-capacity}} = {{(consumed < queue-capacity) ? queue-capacity :
(consumed + minAllocation)}}
Since {{consumed}} never gets over {{queue-capacity}} when MULP is less than
100%, {{queue-capacity}} will never equal {{consumed + minAllocation}}.
I have tested this to verify.
> 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]
