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 "Arun Suresh (JIRA)" <ji...@apache.org> on 2016/10/27 18:42:00 UTC
[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in
QueueMetrics is the same as AllocateMB
[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun Suresh updated YARN-1735:
------------------------------
Labels: oct16-easy (was: )
> For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB
> -----------------------------------------------------------------------
>
> Key: YARN-1735
> URL: https://issues.apache.org/jira/browse/YARN-1735
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Reporter: Siqi Li
> Labels: oct16-easy
> Attachments: YARN-1735.v1.patch, YARN-1735.v2.patch, YARN-1735.v3.patch, YARN-1735.v4.patch
>
>
> in monitoring graphs the AvailableMB of each queue regularly spikes between the AllocatedMB and the entire cluster capacity.
> This cannot be correct since AvailableMB should never be more than the queue max allocation. The spikes are quite confusing since the availableMB is set as the fair share of each queue and the fair share of each queue is bond by their allowed max resource.
> Other than the spiking, the availableMB is always equal to allocatedMB. I think this is not very useful, availableMB for each queue should be their allowed max resource minus allocatedMB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org