hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6279) Add JVM memory usage to JvmMetrics
Date Thu, 08 Oct 2009 18:55:31 GMT

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

Chris Douglas updated HADOOP-6279:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

+1

I committed this. Thanks, Todd!

> Add JVM memory usage to JvmMetrics
> ----------------------------------
>
>                 Key: HADOOP-6279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6279
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.20.2, 0.21.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: hadoop-6279.txt
>
>
> The JvmMetrics currently publish memory usage from the MemoryMXBean. This is useful,
but doesn't include the total heap size (eg as displayed in the JT Web UI).
> It would be nice to expose Runtime.getRuntime().maxMemory() as part of JvmMetrics.
> It seems that Runtime.getRuntime().totalMemory() (used by the JT for "memory used") is
the same as the 'memHeapCommittedM' which already exists.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message