Database Reference
In-Depth Information
High CPU usage
High CPU usage can be associated with frequent Garbage Collections ( GC ). If you see a
lot of GC call information in Cassandra logs and if they take longer than one second to fin-
ish, it means the system has loaded the JVM with the garbage collector.
The easiest fix is to add more nodes. Another option can be to increase the JVM heap size
(adding more RAM, if required) and to tweak the garbage collector setting for Cassandra.
Compaction is a CPU-intensive process. You may expect a spike during compaction. You
should plan to perform a nodetool compaction during relatively silent hours. The same
goes for repair. Execute nodetool repair during low load.
Search WWH ::




Custom Search