Hi Varun, can you elaborate a bit more? I have seen a schema change being pushed, but that was just the first restart. After that, everything has been smooth so far (including several schema changes, all of them verified via "describe").
Thanks! Stefano On Sat, May 20, 2017 at 2:10 AM, Varun Gupta <var...@uber.com> wrote: > We upgraded from 2.2.5 to 3.0.11 and it works fine. I will suggest not to > go with 3.013, we are seeing some issues with schema mismatch due to which > we had to rollback to 3.0.11. > > Thanks, > Varun > > On May 19, 2017, at 7:43 AM, Stefano Ortolani <ostef...@gmail.com> wrote: > > Here (https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt) is > stated that the minimum supported version for the 2.2.X branch is 2.2.2. > > On Fri, May 19, 2017 at 2:16 PM, Nicolas Guyomar < > nicolas.guyo...@gmail.com> wrote: > >> Hi Xihui, >> >> I was looking for this documentation also, but I believe datastax removed >> it, and it is not available yet on the apache website >> >> As far as I remember, intermediate version was needed if C* Version < >> 2.1.7. >> >> You should be safe starting from 2.2.6, but testing the upgrade on a >> dedicated platform is always a good idea. >> >> Nicolas >> >> On 19 May 2017 at 09:02, Xihui He <xihu...@gmail.com> wrote: >> >>> Hi All, >>> >>> We are planning to upgrade our production cluster to 3.x, but I can't >>> find the upgrade guide anymore. >>> Can I upgrade to 3.0.13 from 2.2.6 directly? Is a interim version >>> necessary? >>> >>> Thanks, >>> Xihui >>> >> >> >
