hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siqi Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1735) AvailableMB in QueueMetrics is the same as AllocateMB
Date Fri, 21 Feb 2014 03:30:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

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

    Description: 
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 pool 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.

  was:
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.
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.


> 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 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 pool 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.1.5#6160)

Mime
View raw message