Re: CompletedTasks attribute exposed via JMX

2011-10-12 Thread aaron morton
Storage proxy will give you the total writes through the server, for all CFs. CommitLog thread pool is not what you want. It's not designed to measure the column or row throughput, it's just how many tasks have run through the thread pool. The closest thing to recording the number of columns i

Re: CompletedTasks attribute exposed via JMX

2011-10-12 Thread Alexandru Dan Sicoe
Thanks for the quick replies guys! Just to explain to you why I wanted to understand these two measures, I do batch inserts to Cassandra but the batches are not fixed in size i.e. the number of columns in a batch varies and also the data type of the values placed in the columns varies (the name of

Re: CompletedTasks attribute exposed via JMX

2011-10-11 Thread Tyler Hobbs
The OpsCenter graph you're referring to basically does the following: 1. For each node, find out how much the WriteOperations attribute of the StorageProxy increased during the last minute. 2. Sum these values to get a total for the cluster. 3. Divide by 60 to get an average number of WriteOperati

Re: CompletedTasks attribute exposed via JMX

2011-10-11 Thread aaron morton
Its the number of mutations, a mutation is a collection of changes for a single row across one or more column families. Take a look at the nodetool cfstats, this is where I assume Ops Centre is getting it's data from. Cheers - Aaron Morton Freelance Cassandra Developer @aaro

CompletedTasks attribute exposed via JMX

2011-10-11 Thread Alexandru Dan Sicoe
Hello everyone, I was trying to get some cluster wide statistics of the total insertions performed in my 3 node Cassandra 0.8.6 cluster. So I wrote a nice little program that gets the CompletedTasks attribute of org.apache.cassandra.db:type=Commitlog from every node, sums up the values and records