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 10:5

Re: Cassandra timeout whereas it is not much busy

_flush_writers. Thanks for your help. Nicolas > > Cheers > > - > Aaron Morton > Freelance Cassandra Developer > New Zealand > > @aaronmorton > http://www.thelastpickle.com > > On 29/01/2013, at 4:19 AM, Nicolas Lalevée wrote: > >> I

Re: Cassandra timeout whereas it is not much busy

HitRate Le 23 janv. 2013 à 18:35, Nicolas Lalevée a écrit : > Le 22 janv. 2013 à 21:50, Rob Coli a écrit : > >> On Wed, Jan 16, 2013 at 1:30 PM, Nicolas Lalevée >> wrote: >>> Here is the long story. >>> After some long useless staring at the monitoring g

Re: JMX CF Beans

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

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

Re: Cassandra timeout whereas it is not much busy

Le 22 janv. 2013 à 21:50, Rob Coli a écrit : > On Wed, Jan 16, 2013 at 1:30 PM, Nicolas Lalevée > 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 7u9 >

Re: Cassandra timeout whereas it is not much busy

s for the pointers. I have not tried yet to put our nodes under pressure. But when I'll do, I'll look at those pointers closely. Nicolas > > Hope that helps > > ----- > Aaron Morton > Freelance Cassandra Developer > New Zealand > > @aaronmorton > h

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 e

Re: Dead node still being pinged

> Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 14/06/2012, 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, i

Re: Dead node still being pinged

I think it would be nice if cassandra could resolve itself of that inconsistent state. Nicolas > > > > > - > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 12/06/2012, at 10:33 PM, Nicolas Lalevée wrot

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 à

Re: Dead node still being pinged

-- > Aaron Morton > 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 à 1

Re: Dead node still being pinged

ut it seems that some ResponsePendingTasks needs to end. Nicolas > > Samuel > > > > Nicolas Lalevée > 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

Re: Dead node still being pinged

3263 REMOVAL_COORDINATOR:REMOVER,0 /10.10.0.22 STATUS:removed,42535295865117307932921825928971026432,1336529659203 REMOVAL_COORDINATOR:REMOVER,113427455640312814857969558651062452224 Nicolas > > Samuel > > > > Nicolas Lalevée > 08/06/2012 21:03 > Veuillez répondre à > user@cassandra.a

Re: Dead node still being pinged

reelance Developer > @aaronmorton > http://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

Re: Dead node still being pinged

colas > > > - Message d'origine - > De : Nicolas Lalevée [nicolas.lale...@hibnet.org] > Envoyé : 08/06/2012 19:26 ZE2 > À : user@cassandra.apache.org > Objet : Re: Dead node still being pinged > > > > Le 8 juin 2012 à 15:17, Samuel CARRIERE a écrit :

Re: Dead node still being pinged

to the first 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 > 08/06/2012 14:10 > Veuillez répondre à > user@cassandra.apache.org > >

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 toke