Re: "Ignorning message." showing in the log while upgrade to 0.8

> It's fixed on 0.8.6. For 0.8.5 you would have to build it from source > with the patch applied, yes. > > (Actually, in my opinion this bugfix is a good reason to release 0.8.6.) Turns out I had managed to miss the fact that a 0.8.6 release is being voted on so I'd expect it to happen soonish. Yo

Re: "Ignorning message." showing in the log while upgrade to 0.8

> also not  fixed in 0.8.5?  I am using the binary version of 0.8.5.  Applying > the fix might need to compile it from the source? It's fixed on 0.8.6. For 0.8.5 you would have to build it from source with the patch applied, yes. (Actually, in my opinion this bugfix is a good reason to release 0.

Re: "Ignorning message." showing in the log while upgrade to 0.8

also not fixed in 0.8.5? I am using the binary version of 0.8.5. Applying the fix might need to compile it from the source? On Sun, Sep 18, 2011 at 3:28 AM, Peter Schuller wrote: > >> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to > >> 0.8.5 > > [snip] > > > Yes. It

Re: Local Quorum Performance...

I'm not sure if it's significant, but on first notice the IP addresses all have the same octets in the ProperyFileSnitch, yet the EC2Snitch, all the octets are different. Ergo: PropertyFileSnitch states that are all in the same data centre [168] and the same rac [2]. EC2Snitch states that all n

Re: Local Quorum Performance...

Anthony, We used the Ec2Snitch for one sets of runs, but for another set we're using PropertyFileSnitch. With the PropertyFileSnitch we see: Address DC RackStatus State Load OwnsToken 85070591730234615865843651857942052865 192.168.2.1 us-east 1b

Re: "Ignorning message." showing in the log while upgrade to 0.8

>> I am running local tests about upgrade cassandra.  upgrade from 0.7.4 to >> 0.8.5 [snip] > Yes.  It will take a few exchanges before the new node knows to use > the older protocol with the 0.7 nodes. Not going 0.7.4->0.8.4, due to https://issues.apache.org/jira/browse/CASSANDRA-3166 OP:

Re: Local Quorum Performance...

What snitch do you have configured? We typically see a proper spread of data across all our nodes equally. Anthony On 17/09/2011, at 10:06 AM, Chris Marino wrote: > Hi, I have a question about what to expect when running a cluster across > datacenters with Local Quorum consistency. > > My si

RE: Queue suggestion in Cassandra

ZooKeeper + Menagerie might work, but it's unlikely to have the throughput you require. I'd have a look at Kafka (http://incubator.apache.org/), Kestrel(https://github.com/robey/kestrel/), or one of the AMQP-compliant systems like ActiveMQ (activemq.apache.or

Local Quorum Performance...

Hi, I have a question about what to expect when running a cluster across datacenters with Local Quorum consistency. My simplistic assumption is that the performance of an 8 node cluster split across 2 data centers and running with local quorum would perform roughly the same as a 4 node cluster in

Re: "Ignorning message." showing in the log while upgrade to 0.8

so the schema version not consistent is abnormal? is there a document explains the possible problem while upgrading? I think it might be concerned by many cassandra users. cause if anything unexpected during upgrade, might cause serious problem on production server. cause there is no way to rever