ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tamas Payer (Jira)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-25572) Metrics cannot be stored if mutation size is not set properly
Date Thu, 22 Oct 2020 10:15:00 GMT
Tamas Payer created AMBARI-25572:
------------------------------------

             Summary: Metrics cannot be stored if mutation size is not set properly
                 Key: AMBARI-25572
                 URL: https://issues.apache.org/jira/browse/AMBARI-25572
             Project: Ambari
          Issue Type: Task
          Components: ambari-metrics
    Affects Versions: 2.7.3, 2.7.4, 2.7.5
            Reporter: Tamas Payer


Ambari Metrics Collector sometimes fails to store metric because the batch size settings does
not fit to the current row size and the assembled batch probably does not fit into the maximum
batch memory space.
{code:java}
2020-10-20 10:29:04,752 WARN org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor:
Failed on insert records to store : ERROR 730 (LIM02): MutationState size is bigger than maximum
allowed number of bytes
2020-10-20 10:29:04,752 WARN org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor:
Metric that cannot be stored : [kafka.server.ConsumerGroupMetrics.CommittedOffset.clientId.-.group.console-consumer-46399.partition.0.topic.PREPROD_KAFKA_CBS_TRANSACTION._sum,kafka_broker]{1603186125049=2.65274693E8}{code}
This error can be eliminated by the tweaking of *phoenix.mutate.batchSize* and *phoenix.mutate.batchSizeBytes*
configuration settings.

*Asses the feasibility of changing the AMS implementation that retries upon failure after
manipulation the auto-commit or batch size, or whatever is needed for the successful commit
and notifies the user about sub optimal batch size settings.* 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message