I don't know what is the real cause of my problem. We are still guessing. All operations I have done one cluster are described on timeline: 1.1.7-> 1.2.10 -> upgradesstable -> 2.0.2 -> normal operations ->2.0.3 -> normal operations -> now normal operations means reads/writes/repairs. Could you please, describe briefly how to recover data? I have a problem with scenario described under link: http://thelastpickle.com/blog/2011/12/15/Anatomy-of-a-Cassandra-Partition.html , I can't apply this solution to my case. regards Olek
2014-02-03 Robert Coli <rc...@eventbrite.com>: > On Mon, Feb 3, 2014 at 2:17 PM, olek.stas...@gmail.com > <olek.stas...@gmail.com> wrote: >> >> No, i've done repair after upgrade sstables. In fact it was about 4 >> weeks after, because of bug: > > > If you only did a repair after you upgraded SSTables, when did you have an > opportunity to hit : > > https://issues.apache.org/jira/browse/CASSANDRA-6527 > > ... which relies on you having multiple versions of SStables while > streaming? > > Did you do any operation which involves streaming? (Add/Remove/Replace a > node?) > > =Rob >
