We have upgraded our cassandra version to 2.0.7 and problem has been solved.
Thanks Russ, On Wed, Apr 16, 2014 at 6:46 PM, Russell Hatch <rha...@datastax.com> wrote: > I think you might be seeing the issue reported in > https://issues.apache.org/jira/browse/CASSANDRA-6971 > > If that's the case, it looks like a fix will be in 2.0.7 > > Thanks, > > Russ > > > On Tue, Apr 15, 2014 at 11:48 PM, Umut Kocasaraç <ukocasa...@gmail.com>wrote: > >> Hi Olek, >> >> Could you solve the problem. Because we are experiencing exactly same >> issue. We have 4 nodes and all of them are in different schema. Our >> cassandra version is 2.0.6. >> >> Umut >> >> >> On Fri, Mar 21, 2014 at 12:26 AM, Robert Coli <rc...@eventbrite.com>wrote: >> >>> On Thu, Mar 20, 2014 at 2:23 PM, olek.stas...@gmail.com < >>> olek.stas...@gmail.com> wrote: >>> >>>> Bump one more time, could anybody help me? >>>> >>> >>> Unfortunately, while I can advise you how to resolve "my cluster has >>> multiple schema versions", I have no assistance to offer for "my cluster >>> ends up with split schema versions when I do normal operations." >>> >>> I suggest opening up a JIRA in the apache cassandra JIRA describing what >>> you did and how the result differed from what you expected. >>> >>> =Rob >>> >>> >> >> >
