[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548378#comment-14548378 ]
Hadoop QA commented on YARN-1735: --------------------------------- \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 14m 35s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 1 new or modified test files. | | {color:red}-1{color} | javac | 3m 18s | The patch appears to cause the build to fail. | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12733581/YARN-1735.v2.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 060c84e | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7974/console | This message was automatically generated. > 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 > Attachments: YARN-1735.v1.patch, YARN-1735.v2.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)