Thanks for bringing this up. I've been meaning to for a while now.
I'm at the early stages of doing some testing of Java 11 G1GC vs 17 w/ G1GC
vs 17 w/ Shenandoah. I plan on sharing my results with the wider
community, and if things look good I'll be proposing we remove the
experimental label.
Hi, I was curious if there is a roadmap for graduating JDK17 support for
Cassandra 5.x from experimental to production ready?
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the s
Sartor is right, you should rolling-restart the nodes. Start with the
problematic ones.
If you have multiple schemas in flight (check nodetool describecluster) you
might need to take a more structured approach.
Did you remove/add nodes while schema changes were in progress?
Hi Soyal,
I have encountered similar issues in the past. What has consistently worked for
me is performing a rolling restart of all nodes. If you don’t have tools like
Ansible or scripts to automate the process, I suggest starting by restarting
the node with the problematic schema. That might h
