Hi Pranay,
i seems that your data is unevenly distributed across the cluster with
respect your insertion frequency.Please restructure your partition key
Thanks
On Fri, Jan 20, 2017 at 6:49 AM, Pranay akula
wrote:
> what i have observed is 2-3 old gen GC's in 1-2 mins before OOM which i
> rare
Btw, the C* version is 2.2.5, with several backported patches.
On Sun, Jan 22, 2017 at 10:36 PM, Dikang Gu wrote:
> Hello there,
>
> We have a 100 nodes ish cluster, I find that there are dropped messages on
> random nodes in the cluster, which caused error spikes and P99 latency
> spikes as wel
Hello there,
We have a 100 nodes ish cluster, I find that there are dropped messages on
random nodes in the cluster, which caused error spikes and P99 latency
spikes as well.
I tried to figure out the cause. I do not see any obvious bottleneck in the
cluster, the C* nodes still have plenty of cpu
I cannot tell you were these errors like "Attempting to mutate ..." come
from but under certain circumstances all view mutations are stored in
batches, so the batchlog can grow insanely large. I don't see why a repair
should help you in this situation. I guess what you want is to recreate the
table
Hi there,
Version :- Cassandra 3.0.7
I attempted to create a Materialized View on a certain table and it failed with
never-ending WARN message "Mutation of bytes is too large for the maximum
size of ".
"nodetool stop VIEW_BUILD" also did not help.
That seems to be a result of
https://issues
