[
https://issues.apache.org/jira/browse/AMBARI-14699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107786#comment-15107786
]
Hadoop QA commented on AMBARI-14699:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12783224/AMBARI-14699.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4973//console
This message is automatically generated.
> JMX heatmap API call takes over 1 minute to complete on 900 node cluster
> ------------------------------------------------------------------------
>
> Key: AMBARI-14699
> URL: https://issues.apache.org/jira/browse/AMBARI-14699
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.4.0
>
> Attachments: AMBARI-14699.patch
>
>
> On a 900 node cluster I went to the Dashboard heatmaps page for HDFS and the
> _DataNode Garbage Collection Time_ heatmap took over 1 minute to respond. URL
> call is shown below.
> {code}http://perf-a-1:8080/api/v1/clusters/perf/services/HDFS/components/DATANODE?fields=host_components/metrics/jvm/gcTimeMillis&format=null_padding{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
