hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1156) Change NodeManager AllocatedGB and AvailableGB metrics to show decimal values
Date Mon, 01 Dec 2014 14:16:12 GMT

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

Junping Du commented on YARN-1156:
----------------------------------

Thanks [~ajisakaa] for reporting this bug and [~ozawa] for a quick fix for it. I think our
adding allocatedMB and availableMB here is a good improvement for precisely information. However,
we may want to keep allocatedGB and availableGB there for compatible with upstream projects
(like Apache Ambari, etc.) or 3rd party tools. 
So I suggest we inc/dec MB (container size) to allocatedMB/availableMB, and calculate allocated/availableGB
from allocatedMB/availableMB which make deviation here always in a small range (< 1G or
0.5G if round up).

> Change NodeManager AllocatedGB and AvailableGB metrics to show decimal values
> -----------------------------------------------------------------------------
>
>                 Key: YARN-1156
>                 URL: https://issues.apache.org/jira/browse/YARN-1156
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.1.0-beta
>            Reporter: Akira AJISAKA
>            Assignee: Tsuyoshi OZAWA
>            Priority: Minor
>              Labels: metrics, newbie
>             Fix For: 2.7.0
>
>         Attachments: YARN-1156.1.patch, YARN-1156.2.patch
>
>
> AllocatedGB and AvailableGB metrics are now integer type. If there are four times 500MB
memory allocation to container, AllocatedGB is incremented four times by {{(int)500/1024}},
which means 0. That is, the memory size allocated is actually 2000MB, but the metrics shows
0GB. Let's use float type for these metrics.



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

Mime
View raw message