[
https://issues.apache.org/jira/browse/YARN-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062693#comment-14062693
]
Tassapol Athiapinya commented on YARN-2285:
-------------------------------------------
After closer look, 5000% is valid number. It means 5000% of "guaranteed
capacity" of queue A (about 50% of absolute used capacity). I am making changes
to jira title accordingly. I will also make this improvement jira instead of a
bug.
The point here becomes whether it is nice to "re-label" text in web UI to
better reflect its meaning saying "% used next to queue is % of guaranteed
queue capacity, not absolute used capacity".
> Preemption can cause capacity scheduler to show 5,000% queue absolute used
> capacity.
> ------------------------------------------------------------------------------------
>
> Key: YARN-2285
> URL: https://issues.apache.org/jira/browse/YARN-2285
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.5.0
> Environment: Turn on CS Preemption.
> Reporter: Tassapol Athiapinya
> Attachments: preemption_5000_percent.png
>
>
> I configure queue A, B to have 1%, 99% capacity respectively. There is no max
> capacity for each queue. Set high user limit factor.
> Submit app 1 to queue A. AM container takes 50% of cluster memory. Task
> containers take another 50%. Submit app 2 to queue B. Preempt task containers
> of app 1 out. Turns out capacity of queue B increases to 99% but queue A has
> 5000% used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
