That sounds very interesting Alex, so just to be sure I understand, it was like this 1 - you had 2.1 cluster running with the 2.1 version jar 2 - you upgraded to 3.0, starting the cluster with the 3.0 version jar that has the same strategy name 3 - you changed the compaction strategy to use the built in one?
Another question, did changing the compaction strategy from one twcs to the other trigger merging of old sstables? gil On Thu, Jul 9, 2020 at 4:51 PM Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Thu, Jul 9, 2020 at 3:38 PM Gil Ganz <gilg...@gmail.com> wrote: > >> Hey >> I have a 2.11.4 cluster with tables that are defined with twcs, using >> jeff's jar >> >> https://github.com/jeffjirsa/twcs >> >> All working great, but now I want to upgrade to 3.11, and I have a >> problem, cassandra won't start, it fails on the following error >> > > I guess you'll have to hop through 3.0 first. We did upgrade from 2.1 to > 3.0 by including a twcs.jar built against 3.0 and then altering the table > compaction to use the built-in one, then finally removing the custom jar. > > We had to tweak it a bit for 3.0.15 at the time: > https://github.com/a1exsh/twcs/tree/cassandra-3.0.x > > Regards, > -- > Alex > >
