[
https://issues.apache.org/jira/browse/CASSANDRA-11117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547998#comment-15547998
]
Marcus Eriksson commented on CASSANDRA-11117:
---------------------------------------------
I like the approach in the patch but should we perhaps do;
{code}
if (timeDelta < Long.MAX_VALUE)
metric.colUpdateTimeDeltaHistogram.update(Math.min(18165375903306L,
timeDelta));
{code}
so that we at least record the fact that we had a big time difference? I would
assume operators would be interested in these large deviations (we would
probably need to document that we bunch together everything > 18165375903306L)
> ColUpdateTimeDeltaHistogram histogram overflow
> ----------------------------------------------
>
> Key: CASSANDRA-11117
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11117
> Project: Cassandra
> Issue Type: Bug
> Reporter: Chris Lohfink
> Assignee: Joel Knighton
> Priority: Minor
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> {code}
> getting attribute Mean of
> org.apache.cassandra.metrics:type=ColumnFamily,name=ColUpdateTimeDeltaHistogram
> threw an exceptionjavax.management.RuntimeMBeanException:
> java.lang.IllegalStateException: Unable to compute ceiling for max when
> histogram overflowed
> {code}
> Although the fact that this histogram has 164 buckets already, I wonder if
> there is something weird with the computation thats causing this to be so
> large? It appears to be coming from updates to system.local
> {code}
> org.apache.cassandra.metrics:type=Table,keyspace=system,scope=local,name=ColUpdateTimeDeltaHistogram
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
