AW: Monitoring Cluster with JMX

Unfortunately not, as the nagios JMX check expects a numeric return value and only allows for defining thresholds for issuing warnings or errors depending on that value. It does not allow for post processing the return values. roland Von: Aaron Morton [mailto:aa...@thelastpickle.com] Gesendet:

Re: New feature / educational project

+1 for interest. This feature would be great if done well. On Feb 8, 2011 11:54 PM, "m...@monit.dk" wrote: > I noticed :) > > But the question was if such a feature could make it to the trunk - and as far as I see, there is enough interest around this. > > - Reply message - > From: "Trista

Re: Monitoring Cluster with JMX

If you're using 0.7, I'd skip jmx and use the mx4j http interface then write scripts that convert the data to the format you need. -ryan On Wed, Feb 9, 2011 at 2:47 AM, Roland Gude wrote: > Unfortunately not, as the nagios JMX check expects a numeric return value and > only allows for defining

AW: Monitoring Cluster with JMX

Ah... thanks for the pointer. This should indeed be musch simpler. Thanks. -Ursprüngliche Nachricht- Von: Ryan King [mailto:r...@twitter.com] Gesendet: Mittwoch, 9. Februar 2011 18:11 An: dev@cassandra.apache.org Betreff: Re: Monitoring Cluster with JMX If you're using 0.7, I'd skip jmx

Re: Using Cassandra-cli

Hi Vishan, Aron and all, Thanks for the help. I tried it and successfully worked for me. But I could not find a place where mention about the attributes of some commands. e.g. update column family [with = [and = ...]]; create keyspace [with = [and = ...]]; (we can use comparator=UTF8Type and de

Re: Gossip messages at DEBUG

On Tue, Feb 8, 2011 at 9:01 PM, Aaron Morton wrote: > I've just put the latest 0.7 build on a node and it's logging gossip > messages at DEBUG and making the logs really hard to use. Anyone object to > moving these to TRACE level ? > Moved to TRACE. I think when this was moved from sendRR to sen

Re: Gossip messages at DEBUG

thanks.AOn 10 Feb, 2011,at 08:21 AM, Brandon Williams wrote:On Tue, Feb 8, 2011 at 9:01 PM, Aaron Morton wrote: > I've just put the latest 0.7 build on a node and it's logging gossip > messages at DEBUG and making the logs really hard to use. Anyone object to > moving the

Re: SEVERE Data Corruption Problems

Hi Dan, it would be very useful to test with 0.7 branch instead of 0.7.0 so at least you're not chasing known and fixed bugs like CASSANDRA-1992. As you say, there's a lot of people who aren't seeing this, so it would also be useful if you can provide some kind of test harness where you can say "

RE: SEVERE Data Corruption Problems

I will put two nodes on 0.7. Did you really mean CASSANDRA-1992? I looked over the bug report and patch but cant see how it is related to the problems I have been having. I am not performing bootstraps or repairs and I haven’t since one of the most problematic CFs has been created. I have also look

Re: Using Cassandra-cli

Hi Eranda, you can refer book --> "Cassandra: The Definitive Guide". Also there are web apps(http://github.com/suguru/cassandra-webconsole) which helps to do the same via browser. Also u can follow these article's 1) http://arin.me/blog/wtf-is-a-supercolumn-cassandra-data-model 2) http://maxgrine