[
https://issues.apache.org/jira/browse/CASSANDRA-11117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380061#comment-15380061
]
Joel Knighton commented on CASSANDRA-11117:
-------------------------------------------
The Long.MAX_VALUE in the code snippet you've provided checks for a
Long.MAX_VALUE sentinel value we pass along when there are no relevant column
update deltas in the reconciliation path of the write. This shouldn't be the
problem.
The problem is when certain cells/liveness infos in the reconciliation path
carry very high timestamp values or possibly Long.MIN_VALUE as a timestamp
value (in some of the 3.0 cases).
I can reproduce this in 3.0+; the same methods for reproduction do not work in
2.2. [~urandom], [~jeffery.griffith], you reported this issue on 2.2 clusters.
I see that your cluster was upgraded from an earlier version [~urandom]. Was
yours as well [~jeffery.griffith]?
To help write tests for and validate the fix I have in mind, any details either
of you can share on
- table schemas (in particular, are you using static columns? collections?
counters? user-defined anything?)
- access patterns (insert/updates/deletes)
- ttls/specified timestamps
might help me find a reproduction path for 2.2.
Thanks!
> 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)
