[
https://issues.apache.org/jira/browse/YARN-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732988#comment-15732988
]
Wangda Tan commented on YARN-5889:
----------------------------------
bq. If all apps are asking for resources, then the current algorithm already
does this calculation in the allocation thread.
It may not be true if users uses / asks different resources, and order of
application matters as well.
bq. I believe that N is the number of users, not applications. So,
theoretically, the calculations could be based on each user's used value. Is
that accurate?
Maybe not, as I mentioned above, order of application matters. Per my
understanding, we have to iterate all apps according to FIFO order and
calculate UL.
> 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.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]
