Thanks Robert, you are right, I upgraded to 2.0.1 and don't fix the problem, 2 of 3 nodes raise the same error after 30 minutes.
I will try to create a new cluster 1.2 and copy data, can you tell me please the best pratice to do this, do i have to use sstable2json / json2sstable or other method. Thanks, 2013/10/21 Robert Coli <rc...@eventbrite.com> > On Mon, Oct 21, 2013 at 2:17 AM, Kais Ahmed <k...@neteck-fr.com> wrote: > >> We have recently run in production a new cluster C* 2.0.0 with 3 nodes RF >> 3. >> > > https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/ > > "What Version of Cassandra Should I Run in Production?" > > If I were you I would probably try to read my data into a 1.2.x cluster. > Downgrading versions on the same cluster is unlikely to work. You could try > going to 2.0.1 but there is not compelling reason to believe this will fix > your problem. > > =Rob > > >
