incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Kuebrich <dan.kuebr...@gmail.com>
Subject Re: Cassandra Monitoring
Date Fri, 17 Dec 2010 21:11:30 GMT
Is anyone using cassandra with monit?  All I have is this embarrassing bit
of monit config:

check process cassandra with pidfile /var/run/cassandra.pid
  start program = "/etc/init.d/cassandra start" with timeout 60 seconds
  stop program  = "/etc/init.d/cassandra stop"
  if failed port 9160 type tcp
     with timeout 15 seconds
     then restart
  if 3 restarts within 5 cycles then timeout
  group server

I'm sure there's some good numbers available via JMX to alert on as well but
I'm not sure best way to poll it from monit.  Comments/contributions
appreciated.

dan

On Fri, Dec 17, 2010 at 11:03 AM, Edward Capriolo <edlinuxguru@gmail.com>wrote:

> On Fri, Dec 17, 2010 at 5:48 AM, Daniel Doubleday
> <daniel.doubleday@gmx.net> wrote:
> > Hi all
> > just wanted to share a simple way we use to monitor cassandra internals
> with
> > zabbix.
> > We use a minimal http server which reads jmx and shows returns them in a
> > property form. Thats read by zabbix every 30secs.
> > That's started together with cassandra:
> > https://gist.github.com/744761
> > Output looks something like:
> > dd@caladan[~]$ curl http://b22:9090/jmxexport
> > OperationMode=Normal
> > Load=151.379
> > ReadOperations=506334
> > WriteOperations=865867
> > TotalReadLatencyMicros=6663882635
> > TotalWriteLatencyMicros=352292885
> > BytesCompacted=0
> > BytesTotalInProgress=0
> > PendingTasks=0
> > HeapUsed=1153810280
> > How / what are you monitoring? Best practices someone?
> > Cheers,
> > Daniel Doubleday,
> > smeet.com, Berlin
>
> Using cacti and - >
> http://www.jointhegrid.com/cassandra/cassandra-cacti-m6.jsp
> Many people are using munin good support there.
>
> Best Bractices:
> Monitor SSTable sizes and growth.
> Monitor Reads/Write sec
> Monitor Cache hit rate
> Monitor Compactions (what % of the day and average node is compacting)
> Monitor SSTable count (make sure you do not have to many)
> Monitor IO wait. (make sure you are not disk bound)
> Monitor JVM memory (make sure you have some overhead for bursts of traffic)
>

Mime
View raw message