[
https://issues.apache.org/jira/browse/CASSANDRA-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Yeksigian updated CASSANDRA-8028:
--------------------------------------
Attachment: 8028-2.1.txt
This overflow is persisted in the sstable metadata that you have produced.
There are probably very large partitions which are overflowing our histogram.
In order to get around this, we'll need to increase the amount of data that is
persisted and break compatibility of nodetool, so it will have to wait for 3.0.
I have attached a check so that the other information can be gathered, except
for the metric that has overflowed.
> 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
> 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)
