You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/09/10 23:56:53 UTC
[jira] [Updated] (AMBARI-3178) Incorrect HDFS Garbage Collection
Time on Heatmap
[ https://issues.apache.org/jira/browse/AMBARI-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-3178:
------------------------------------
Summary: Incorrect HDFS Garbage Collection Time on Heatmap (was: Incorrect HDFS Garbage Collection Time on "Heatmap")
> Incorrect HDFS Garbage Collection Time on Heatmap
> -------------------------------------------------
>
> Key: AMBARI-3178
> URL: https://issues.apache.org/jira/browse/AMBARI-3178
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.4.1
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.4.1
>
> Attachments: AMBARI-3178.patch
>
>
> Precondition: hadoop is installed with default settings.
> Steps:
> 1. Go to "Heatmaps" page.
> 2. Select "HDFS Garbage Collection Time" metric
> Result:
> Random hosts indicate large HDFS Garbage Collection Time(more than 1d).
> JMX value of GcTimeMillis is normal.
> API call:
> {code}
> http://<ambari-server-host>:8080/api/v1/clusters/c1/services/HDFS/components/DATANODE?fields=host_components/metrics/jvm/gcTimeMillis&_=1378849540894
> {code}
--
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