AW: [VOTE RESULT] was: [VOTE] 0.7.0 rc2
Hi everybody Glad that rc2 is out now! Will it be available in riptano mvn repository? Greetings, Roland -Ursprüngliche Nachricht- Von: Eric Evans [mailto:eev...@rackspace.com] Gesendet: Freitag, 10. Dezember 2010 00:30 An: dev@cassandra.apache.org Betreff: [VOTE RESULT] was: [VOTE] 0.7.0 rc2 On Mon, 2010-12-06 at 12:25 -0600, Eric Evans wrote: > There have been quite a few changes[1] since the release of RC1, too > many to not seek wider testing. I propose the following for release as > 0.7.0 RC2. > > SVN: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-...@r1042731 > 0.7.0-rc2 artifacts: http://people.apache.org/~eevans > > The vote will be open for the usual 72 hours. That makes 3 +1s and no -1s, the vote passes. I'll get everything published before the day is out. Thanks! -- Eric Evans eev...@rackspace.com
Monitoring Cluster with JMX
Hello, we are trying to monitor our cassandra cluster with Nagios JMX checks. While there are JMX attributes which expose the list of reachable/unreachable hosts, it would be very helpful to have additional numeric attributes exposing the size of these lists. This could be used to set thresholds (in Nagios monitoring) i.e. at least 3 hosts must be reachable before Nagios issues a warning. This is probably not hard to do and we are willing to implement/supply patches if someone could point us in the right direction on where to implement it. Greetings, roland -- YOOCHOOSE GmbH Roland Gude Software Engineer Im Mediapark 8, 50670 Köln +49 221 4544151 (Tel) +49 221 4544159 (Fax) +49 171 7894057 (Mobil) Email: roland.g...@yoochoose.com WWW: www.yoochoose.com<http://www.yoochoose.com/> YOOCHOOSE GmbH Geschäftsführer: Dr. Uwe Alkemper, Michael Friedmann Handelsregister: Amtsgericht Köln HRB 65275 Ust-Ident-Nr: DE 264 773 520 Sitz der Gesellschaft: Köln
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: Dienstag, 8. Februar 2011 21:32 An: dev@cassandra.apache.org Betreff: Re: Monitoring Cluster with JMX Can't you get the length of the list on the monitoring side of things ? aaron On 08 Feb, 2011,at 10:25 PM, Roland Gude wrote: Hello, we are trying to monitor our cassandra cluster with Nagios JMX checks. While there are JMX attributes which expose the list of reachable/unreachable hosts, it would be very helpful to have additional numeric attributes exposing the size of these lists. This could be used to set thresholds (in Nagios monitoring) i.e. at least 3 hosts must be reachable before Nagios issues a warning. This is probably not hard to do and we are willing to implement/supply patches if someone could point us in the right direction on where to implement it. Greetings, roland -- YOOCHOOSE GmbH Roland Gude Software Engineer Im Mediapark 8, 50670 Köln +49 221 4544151 (Tel) +49 221 4544159 (Fax) +49 171 7894057 (Mobil) Email: roland.g...@yoochoose.com<mailto:roland.g...@yoochoose.com> WWW: www.yoochoose.com<http://www.yoochoose.com/<http://www.yoochoose.com%3chttp:/www.yoochoose.com/>> YOOCHOOSE GmbH Geschäftsführer: Dr. Uwe Alkemper, Michael Friedmann Handelsregister: Amtsgericht Köln HRB 65275 Ust-Ident-Nr: DE 264 773 520 Sitz der Gesellschaft: Köln
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 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 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: Dienstag, 8. Februar 2011 21:32 > An: dev@cassandra.apache.org > Betreff: Re: Monitoring Cluster with JMX > > Can't you get the length of the list on the monitoring side of things ? > aaron > On 08 Feb, 2011,at 10:25 PM, Roland Gude wrote: > Hello, > > we are trying to monitor our cassandra cluster with Nagios JMX checks. While > there are JMX attributes which expose the list of reachable/unreachable > hosts, it would be very helpful to have additional numeric attributes > exposing the size of these lists. This could be used to set thresholds (in > Nagios monitoring) i.e. at least 3 hosts must be reachable before Nagios > issues a warning. > This is probably not hard to do and we are willing to implement/supply > patches if someone could point us in the right direction on where to > implement it. > > Greetings, > roland > > -- > YOOCHOOSE GmbH > > Roland Gude > Software Engineer > > Im Mediapark 8, 50670 Köln > > +49 221 4544151 (Tel) > +49 221 4544159 (Fax) > +49 171 7894057 (Mobil) > > > Email: roland.g...@yoochoose.com<mailto:roland.g...@yoochoose.com> > WWW: > www.yoochoose.com<http://www.yoochoose.com/<http://www.yoochoose.com%3chttp:/www.yoochoose.com/>> > > YOOCHOOSE GmbH > Geschäftsführer: Dr. Uwe Alkemper, Michael Friedmann > Handelsregister: Amtsgericht Köln HRB 65275 > Ust-Ident-Nr: DE 264 773 520 > Sitz der Gesellschaft: Köln > -- -@rk
AW: interest in creating a "cassandra-gossip" library?
Hi, Is there any progress on this topic? I would really like to see such a library. -Ursprüngliche Nachricht- Von: matthew hawthorne [mailto:mhawtho...@gmail.com] Gesendet: Mittwoch, 22. Dezember 2010 20:07 An: dev@cassandra.apache.org Betreff: interest in creating a "cassandra-gossip" library? hello, I'm starting a project at my day job to deploy a gossip protocol implementation. part of my initial work is to evaluate existing implementations. being loosely familiar with Cassandra, I read http://wiki.apache.org/cassandra/ArchitectureGossip and have looked over the related code a bit. is there interest in breaking out the gossip-related portions of Cassandra into a library that could be reused by other projects? I work on a team that is ready and willing to contribute heavily. we'd just need some guidance as to how to structure the Cassandra subcomponent(s) and properly integrate them with the builds, tests, etc. here are a few examples of functionality we're looking to add: 1) hierarchical state - our use case is cross data center gossip, where we don't want every node in the 2 clusters communicating, but do want a node from cluster1 to send a summary of the cluster's state to cluster2, and vice versa. essentially I'm talking about rolling up the state of multiple nodes into a single "virtual" node 2) mutual authentication - nodes verifying the identity of other nodes before gossipping 3) encryption - encrypted traffic, especially for the cross data center case any opinions on this? thanks in advance for any feedback! -matt
AW: How is Cassandra being used?
I think it is a very good idea to gather such information and to make it easy for the users who want to or don't care and to consider the "twitchiness" as well. How about putting the reporting code in a separate module/jar and report statistics if the jar is there and don’t if it is not (similar as it is done with using native stuff if JNA is there) The one could provide to binary archives on the homepage. One with the jar and one without. That way people who do not want the code simply select the shipment where it is not included or delete the jar. You could - (and should) - even stick a "Enable/Disable" switch on top of it. -Ursprüngliche Nachricht- Von: Dave Brosius [mailto:dbros...@baybroadband.net] Gesendet: Mittwoch, 16. November 2011 02:25 An: dev@cassandra.apache.org Betreff: Re: How is Cassandra being used? +1 for an opt-in approach. To get better opt-in rates perhaps prompt for it on start (once) rather than hope folks find it buried in the yaml Eric Evans wrote: >On Tue, Nov 15, 2011 at 11:23 PM, Jonathan Ellis wrote: >> I started a "users survey" thread over on the users list (replies are >> still trickling in), but as useful as that is, I'd like to get >> feedback that is more quantitative and with a broader base. This will >> let us prioritize our development efforts to better address what >> people are actually using it for, with less guesswork. For instance: >> we put a lot of effort into compression for 1.0.0; if it turned out >> that only 1% of 1.0.x users actually enable compression, then it means >> that we should spend less effort fine-tuning that moving forward, and >> use the energy elsewhere. >> >> (Of course it could also mean that we did a terrible job getting the >> word out about new features and explaining how to use them, but either >> way, it would be good to know!) >> >> I propose adding a basic cluster reporting feature to cassandra.yaml, >> enabled by default. It would send anonymous information about your >> cluster to an apache.org VM. Information like, number (but not names) >> of keyspaces and columnfamilies, ks-level options like compression, cf >> options like compaction strategy, data types (again, not names) of >> columns, average row size (or better: the histogram data), and average >> sstables per read. >> >> Thoughts? > >I think this is potentially quite dangerous; There are a lot people >who get very twitchy at the idea of software that Phones Home. I've >seen this so many times, and in all cases it was for software a lot >less sensitive than a database. > >I'm sure you've already considered this though, you're already talking >about anonymity, and transparency, and what I assume is neutrality of >the collection endpoint (can apache actually provide a VM; is that a >thing?). I'm just afraid that we'll scare people off before they can >be properly convinced that it's all on the up-and-up. > >I'm curious to see what others think, but at the moment I'm hovering >somewhere around a -0 if it were opt-in (off by default). > >-- >Eric Evans >Acunu | http://www.acunu.com | @acunu
