You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Tassapol Athiapinya (JIRA)" <ji...@apache.org> on 2014/07/15 23:43:05 UTC
[jira] [Updated] (YARN-2285) Preemption can cause capacity
scheduler to show 5,000% queue capacity.
[ https://issues.apache.org/jira/browse/YARN-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tassapol Athiapinya updated YARN-2285:
--------------------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
Summary: Preemption can cause capacity scheduler to show 5,000% queue capacity. (was: Preemption can cause capacity scheduler to show 5,000% queue absolute used capacity.)
> Preemption can cause capacity scheduler to show 5,000% queue capacity.
> ----------------------------------------------------------------------
>
> Key: YARN-2285
> URL: https://issues.apache.org/jira/browse/YARN-2285
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
> Affects Versions: 2.5.0
> Environment: Turn on CS Preemption.
> Reporter: Tassapol Athiapinya
> Priority: Minor
> 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)