If you have a fork of Cassandra with custom patches and build/execute the dtest suite as part of qualification, you’d want to upgrade that as well.
Note that in more recent 3.0.x releases, the project also introduced in-JVM dtests. This is a new suite that serves a similar purpose to the Python dtests, but which are much more reliable and allow for spawning of multiple C* instances in a JVM for testing. I’d recommend adding this to your build/CI process if so. If you don’t have a fork and deploy stock builds of Cassandra, you probably don’t need to worry about the dtest repo. - Scott > On Jun 13, 2022, at 10:36 PM, Jaydeep Chovatia <chovatia.jayd...@gmail.com> > wrote: > > > Thanks Jeff and Scott for valuable feedback! > One more question, do we have to upgrade the dTest repo if we go to 3.0.27, > or the one we have currently already working with 3.0.14 should continue to > work fine? > > Jaydeep > >> On Mon, Jun 13, 2022 at 10:25 PM C. Scott Andreas <sc...@paradoxica.net> >> wrote: >> Thank you for reaching out, and for planning the upgrade! >> >> Upgrading from 3.0.14 to 3.0.27 would be best, followed by upgrading to >> 4.0.4. >> >> 3.0.14 contains a number of serious bugs that are resolved in more recent >> 3.0.x releases (3.0.19+ are generally good/safe). Upgrading to 3.0.27 will >> put you on a great 3.0.x build. If all looks good from there, you should >> have an easy upgrade to 4.0.4. >> >> I would not recommend passing through intermediate 3.0.x releases on the way >> to 3.0.27; doing so is not necessary. >> >> Cheers, >> >> - Scott >> >> >>>> On Jun 13, 2022, at 10:17 PM, Runtian Liu <curly...@gmail.com> wrote: >>>> >>> >>> Hi, >>> >>> I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am >>> planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe >>> manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0. >>> >>> As you know, there are multiple minor releases between 3.0.14 and 3.0.26, >>> so I am planning to upgrade in 2-3 batches say 1) 3.0.14 → 3.0.16 2) 3.0.16 >>> to 3.0.20 3) 3.0.20 → 3.0.26. >>> . Do you have suggestions or anything that I need to be aware of? Is there >>> any minor release between 3.0.14 and 3.0.26, which is not safe etc.? >>> >>> Best regards. >>>
