You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Luke Lu (JIRA)" <ji...@apache.org> on 2013/06/02 05:35:21 UTC

[jira] [Commented] (HADOOP-9560) metrics2#JvmMetrics should have max memory size of JVM

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

Luke Lu commented on HADOOP-9560:
---------------------------------

Should've used memHeap.getMax() to be more concise and consistent with the rest of the code.
                
> metrics2#JvmMetrics should have max memory size of JVM
> ------------------------------------------------------
>
>                 Key: HADOOP-9560
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9560
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Tsuyoshi OZAWA
>            Assignee: Tsuyoshi OZAWA
>            Priority: Minor
>             Fix For: 2.1.0-beta
>
>         Attachments: HADOOP-9560.1.patch
>
>
> metrics#JvmMetrics have the max memory size of JVM specified by -Xmx option.
> metrics2#JvmMetrics doesn't have it but it should also have max memory size of JVM, because it's useful for users.

--
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