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 "Siqi Li (JIRA)" <ji...@apache.org> on 2014/02/19 20:50:19 UTC

[jira] [Updated] (YARN-1735) 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 ]

Siqi Li updated YARN-1735:
--------------------------

    Description: 
in Viz 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 pool max allocation. 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.

> 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: resourcemanager, scheduler
>            Reporter: Siqi Li
>
> in Viz 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 pool max allocation. 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.1.5#6160)