[
https://issues.apache.org/jira/browse/YARN-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044311#comment-18044311
]
ASF GitHub Bot commented on YARN-10390:
---------------------------------------
github-actions[bot] commented on PR #2198:
URL: https://github.com/apache/hadoop/pull/2198#issuecomment-3639488878
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> LeafQueue: retain user limits cache across assignContainers() calls
> -------------------------------------------------------------------
>
> Key: YARN-10390
> URL: https://issues.apache.org/jira/browse/YARN-10390
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler, capacityscheduler
> Reporter: Muhammad Samir Khan
> Assignee: Muhammad Samir Khan
> Priority: Major
> Fix For: 3.2.2, 3.4.0, 3.3.1
>
> Attachments: YARN-10390-branch-3.1.002.patch,
> YARN-10390-branch-3.2.002.patch, YARN-10390.002.patch, user limit caching
> profile.pdf
>
>
> Currently, user limits are cached locally in leafQueue.assignContainers call
> to avoid repeating some steps. This cache can be retained across the calls.
> Will put up a PR soon. Profiling was done using the proposed changes in
> TestCapacitySchedulerPerf.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
