[
https://issues.apache.org/jira/browse/CASSANDRA-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158454#comment-14158454
]
Carl Yeksigian commented on CASSANDRA-8028:
-------------------------------------------
These metrics are captured per-sstable, it is possible that the change in
behaviour is down to a compaction.
The max partition size is already right at the boundary of not being
representable by the histograms, so any difference in the sstables could be
enough to change whether the histogram is overflowed or not.
> Unable to compute when histogram overflowed
> -------------------------------------------
>
> Key: CASSANDRA-8028
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8028
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: Linux
> Reporter: Gianluca Borello
> Assignee: Carl Yeksigian
> Fix For: 2.1.1
>
> Attachments: 8028-2.1.txt
>
>
> It seems like with 2.1.0 histograms can't be computed most of the times:
> $ nodetool cfhistograms draios top_files_by_agent1
> nodetool: Unable to compute when histogram overflowed
> See 'nodetool help' or 'nodetool help <command>'.
> I can probably find a way to attach a .cql script to reproduce it, but I
> suspect it must be obvious to replicate it as it happens on more than 50% of
> my column families.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
