Thank you very much. I figured out the number of tables is the cause yesterday.
Your analysis confirmed that.
在2015年10月25 05时23分, "Graham Sanderson"写道:
I would imagine you are running on fairly slow machines (given the CPU usage),
but 2.0.12 and 2.1 use a fairly old version of the yammer/c
I would imagine you are running on fairly slow machines (given the CPU usage),
but 2.0.12 and 2.1 use a fairly old version of the yammer/codehale metrics
library.
It is waking up every 5 seconds, and updating Meters… there are a bunch of
these Meters per table (embedded in Timers), so your larg
I saw an average 10% cpu usage on each node when the cassandra cluster has no
load at all.
I checked which thread was using the cpu, and I got the following 2 metric
threads each occupying 5% cpu.
jstack output:
"metrics-meter-tick-thread-2" daemon prio=10 tic=...
java.lang.Thread.State
