Upgrade 1.2.11 to 2.0.6: some errors

Hi, On our test cluster, we tried a upgrade of Cassandra from 1.22.1 to 2.0.6. It was not straight forward so I would like to know if it is expected, so I can do it safely on prod. The first time we tried, the first upgrading node refused to start with this error: ERROR [main] 2014-03-19

Re: Cassandra timeout whereas it is not much busy

Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 29/01/2013, at 4:19 AM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: I did some testing, I have a theory. First, we have it seems a lot of CF. And two are particularly every hungry in RAM, consuming

Re: Cassandra timeout whereas it is not much busy

:35, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 22 janv. 2013 à 21:50, Rob Coli rc...@palominodb.com a écrit : On Wed, Jan 16, 2013 at 1:30 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Here is the long story. After some long useless staring at the monitoring graphs, I

Re: JMX CF Beans

thanks. both of you. Nicolas Le 25 janv. 2013 à 19:05, Tyler Hobbs ty...@datastax.com a écrit : On Fri, Jan 25, 2013 at 8:07 AM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Just a quick question about the attributes exposed via JMX. I have some doc [1] but it doesn't help about CF

JMX CF Beans

Just a quick question about the attributes exposed via JMX. I have some doc [1] but it doesn't help about CF beans. The BloomFilterFalseRatio, is that the ratio of found vs missed, or the ratio of false positive vs the number of tests, or something else ? The ReadCount and WriteCount, how do

Re: Cassandra timeout whereas it is not much busy

Le 22 janv. 2013 à 21:50, Rob Coli rc...@palominodb.com a écrit : On Wed, Jan 16, 2013 at 1:30 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Here is the long story. After some long useless staring at the monitoring graphs, I gave a try to using the openjdk 6b24 rather than openjdk

Re: Cassandra timeout whereas it is not much busy

. Nicolas Hope that helps - Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 17/01/2013, at 10:30 AM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Hi, I have a strange behavior I am not able to understand. I

Cassandra timeout whereas it is not much busy

Hi, I have a strange behavior I am not able to understand. I have 6 nodes with cassandra-1.0.12. Each nodes have 8G of RAM. I have a replication factor of 3. --- my story is maybe too long, trying shorter here, while saving what I wrote in case someone has patience to read my bad

Re: Dead node still being pinged

, at 12:06 AM, Nicolas Lalevée wrote: Le 13 juin 2012 à 10:30, aaron morton a écrit : Here is what I *think* is going on, if Brandon is around he may be able to help out. The old nodes are being included in the Gossip rounds, because Gossiper.doGossipToUnreachableMember() just looks

Re: Dead node still being pinged

://www.thelastpickle.com On 12/06/2012, at 10:33 PM, Nicolas Lalevée wrote: I have one dirty solution to try: bring data-2 and data-4 back up and down again. Is there any way I can tell cassandra to not get any data, so when I would get my old node up, no streaming would start ? cheers, Nicolas

Re: Dead node still being pinged

Freelance Developer @aaronmorton http://www.thelastpickle.com On 12/06/2012, at 3:33 AM, Nicolas Lalevée wrote: finally, thanks to the groovy jmx builder, it was not that hard. Le 11 juin 2012 à 12:12, Samuel CARRIERE a écrit : If I were you, I would connect (through JMX, with jconsole

Re: Dead node still being pinged

I have one dirty solution to try: bring data-2 and data-4 back up and down again. Is there any way I can tell cassandra to not get any data, so when I would get my old node up, no streaming would start ? cheers, Nicolas Le 12 juin 2012 à 12:25, Nicolas Lalevée a écrit : Le 12 juin 2012 à 11

Re: Dead node still being pinged

REMOVAL_COORDINATOR:REMOVER,113427455640312814857969558651062452224 Nicolas Samuel Nicolas Lalevée nicolas.lale...@hibnet.org 08/06/2012 21:03 Veuillez répondre à user@cassandra.apache.org A user@cassandra.apache.org cc Objet Re: Dead node still being pinged Le 8 juin

Re: Dead node still being pinged

. Nicolas Samuel Nicolas Lalevée nicolas.lale...@hibnet.org 08/06/2012 21:03 Veuillez répondre à user@cassandra.apache.org A user@cassandra.apache.org cc Objet Re: Dead node still being pinged Le 8 juin 2012 à 20:02, Samuel CARRIERE a écrit : I'm in the train

Dead node still being pinged

I had a configuration where I had 4 nodes, data-1,4. We then bought 3 bigger machines, data-5,7. And we moved all data from data-1,4 to data-5,7. To move all the data without interruption of service, I added one new node at a time. And then I removed one by one the old machines via a remove

Re: Dead node still being pinged

of my new node What version of cassandra are you using ? Sorry I should have wrote this in my first mail. I use the 1.0.9 Nicolas Samuel Nicolas Lalevée nicolas.lale...@hibnet.org 08/06/2012 14:10 Veuillez répondre à user@cassandra.apache.org A user@cassandra.apache.org cc

Re: Dead node still being pinged

://www.thelastpickle.com On 9/06/2012, at 12:10 AM, Nicolas Lalevée wrote: I had a configuration where I had 4 nodes, data-1,4. We then bought 3 bigger machines, data-5,7. And we moved all data from data-1,4 to data-5,7. To move all the data without interruption of service, I added one new node