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 "Akira AJISAKA (JIRA)" <ji...@apache.org> on 2013/09/06 02:55:51 UTC

[jira] [Updated] (YARN-1156) Change NodeManager AllocatedGB and AvailableGB metrics to show decimal values

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

Akira AJISAKA updated YARN-1156:
--------------------------------

    Description: 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.  (was: 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 long type for these metrics.)
    
> 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
>            Priority: Minor
>              Labels: metrics, newbie
>             Fix For: 2.3.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira