cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8028) Unable to compute when histogram overflowed
Date Thu, 23 Oct 2014 20:31:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181904#comment-14181904
] 

Brandon Williams commented on CASSANDRA-8028:
---------------------------------------------

bq. This will still be a breaking change which should wait until 3.0. nodetool currently expects
the size of the buckets to always be 90, and will fail an assertion if we make changes on
the server to send the full histogram to the client.

But we don't need to allow mixing an older nodetool with a newer server or vice versa, so
can't we change them both in 2.1?

> 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.2
>
>         Attachments: 8028-2.1.txt, 8028-trunk.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)

Mime
View raw message