Hi Aaron, list,
Thanks for the input. But... We figured out what the reason is:
https://issues.apache.org/jira/browse/CASSANDRA-5677
we've eliminated the two major spots where we did deletes and things
have calmed down. Timeouts still happen and we're eagerly awaiting 1.2.7.
Cheers
Steffen
> It started with Cassandra 1.1.10 and on Friday we've migrated to 1.2.6 and
> now we have the issue that flushes are no longer executed automatically - we
> have to do them every hour by hand (nodetool flush) in order to keep the
> nodes on an acceptable utilizatzion level. Without manual flush
The heap size is 3GB and the GC has to run only every 30 minutes... I'm
pretty sure increasing heap won't help.
Am 08.07.2013 11:15, schrieb Radim Kolar:
Without manual flush the CPU goes mad after a couple of hours on each
instance.
increase heap size
--
Steffen Rusitschka
CTO
MegaZebra
Without manual flush the CPU goes mad after a couple of hours on each
instance.
increase heap size
Hi cassandra list,
we are having in issue in one of our Cassandra clusters where all 3
nodes with RF 3 have 22 pending tasks (nodetool compactionstats) since
mid of April that are never be executed. Even after a restart they show up.
It started with Cassandra 1.1.10 and on Friday we've migrat
