[
https://issues.apache.org/jira/browse/AMBARI-14088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028995#comment-15028995
]
Hadoop QA commented on AMBARI-14088:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12774528/AMBARI-14088_2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4410//console
This message is automatically generated.
> Add GC tuning params to Collector daemon similar to HBase
> ---------------------------------------------------------
>
> Key: AMBARI-14088
> URL: https://issues.apache.org/jira/browse/AMBARI-14088
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-upgrade, stacks
> Affects Versions: 2.1.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14088_2.patch
>
>
> Presently we resort to all defaults. We can optimize this much better by
> doing some memory profiling on the collector.
> Error trace:
> {code}
> javax.ws.rs.WebApplicationException:
> org.apache.phoenix.exception.PhoenixIOException:
> org.apache.phoenix.exception.PhoenixIOException:
> org.apache.hadoop.hbase.DoNotRetryIOException:
> METRIC_RECORD,,1447979747302.84e03f0ea4ac1ba9d0dde2ce14d0c878.: Requested
> memory of 31743360 bytes could not be allocated from remaining memory of
> 69028112 bytes from global pool of 96642662 bytes after waiting for 10000ms.
> at
> org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:84)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
