hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong
Date Tue, 05 Jan 2016 21:32:39 GMT

    [ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083846#comment-15083846
] 

Wangda Tan commented on YARN-4538:
----------------------------------

Thanks for reporting this issue, [~bibinchundatt].

The root cause is like what you said, _incrPendingResource and _decrPendingResource have different
implementations.

I think there're two fixes needed:
- Add {{max(containers, 1)}} to _incrPendingResources
- Caller of {{QueueMetrics#incrPendingResources/decrPendingResources}} should avoid calling
it when #containers == 0, and it's not a decrease/increase container.

Thoughts?

> QueueMetrics pending  cores and memory metrics wrong
> ----------------------------------------------------
>
>                 Key: YARN-4538
>                 URL: https://issues.apache.org/jira/browse/YARN-4538
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>
> Submit 2 application to default queue 
> Check queue metrics for pending cores and memory
> {noformat}
>     List<QueueInfo> allQueues = client.getChildQueueInfos("root");
>     for (QueueInfo queueInfo : allQueues) {
>       QueueStatistics quastats = queueInfo.getQueueStatistics();
>       System.out.println(quastats.getPendingVCores());
>       System.out.println(quastats.getPendingMemoryMB());
>     }
> {noformat}
> *Output :*
> -20
> -20480



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message