[
https://issues.apache.org/jira/browse/CASSANDRA-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200343#comment-17200343
]
Caleb Rackliffe commented on CASSANDRA-15164:
---------------------------------------------
[~blerer] [~clohfink] I've reworked the patch a bit to handle both of the stats
histograms and take into account the feedback
[here|https://github.com/apache/cassandra/pull/750#pullrequestreview-493580468].
Short of dynamically growing the number of buckets, this seems like the most
reasonable quick fix to make the things that might depend on an overflowed
histogram safe. (The worst case is that our estimates won't be as helpful as
they would if we had more buckets, etc.)
> Overflowed Partition Cell Histograms Can Prevent Compactions from Executing
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-15164
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15164
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
> Reporter: Ankur Jha
> Assignee: Caleb Rackliffe
> Priority: Urgent
> Labels: compaction, partition
> Fix For: 4.0-beta
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Hi, we are running 6 node Cassandra cluster in production with 3 seed node
> but from last night one of our seed nodes is continuously throwing an error
> like this;-
> cassandra.protocol.ServerError: <Error from server: code=0000 [Server error]
> message="java.lang.IllegalStateException: Unable to compute ceiling for max
> when histogram overflowed">
> For a cluster to be up and running I Drained this node.
> Can somebody help me out with this?
>
> Any help or lead would be appreciated
>
> Note : We are using Cassandra version 3.7
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
