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

Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/11/27 02:48:35 UTC

[jira] [Reopened] (AMBARI-3852) 'memMaxM' is required for NameNode from metrics/jvm call

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

Yusaku Sako reopened AMBARI-3852:
---------------------------------


Reopening, as memMaxM is not coming thru for NameNode when I tested on branch-1.4.2, 263ac8b5d57dd53093eb6b3405c0ab66fbc640b8.

> 'memMaxM' is required for NameNode from metrics/jvm call
> --------------------------------------------------------
>
>                 Key: AMBARI-3852
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3852
>             Project: Ambari
>          Issue Type: Task
>          Components: agent
>    Affects Versions: 1.4.2
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3852_1.4.2.patch, AMBARI-3852_trunk.patch
>
>
> The API call can get 'memMaxM' value from ResourceManager , but for NameNode and HbaseMaster this value are missing.
> We need this value for NameNode and Hbase Master from backend to calculate the correct Heap value.



--
This message was sent by Atlassian JIRA
(v6.1#6144)