I think Isaeed may be referring to the setCompactionParametersJson JMX method (https://issues.apache.org/jira/browse/CASSANDRA-9965, https://github.com/apache/cassandra/blob/cassandra-5.0.6/src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java#L109 )
This is a good way of evaluating a new compaction configuration, but it's probably not worth rolling out a compaction change on one node at a time unless you are really super risk-averse. Maybe try it out on one node and observe a little bit, and if everything looks good then just make the alter call like Patrick suggests. Ideally you'd have a test environment with a similar data size that you could test the compaction change against. Unless you are running pretty close to the edge of disk or cpu utilization, it should be fine to alter the compaction strategy, but the JMX call could be a useful tool to try it out on a canary node and observe how things work. Thanks, Andy On Mon, Nov 24, 2025 at 10:08 AM Patrick McFadin <[email protected]> wrote: > I tried to find the previous discussion about JMX you are referring too, > but didn’t find it. > > In general, if you are switching to UCS, just use the alter statement. If > that isn’t working for you or you have some special circumstance, it would > be good to know what that is so we can address the problem. > > Patrick > > On Nov 20, 2025, at 1:34 AM, Isaeed Mohanna <[email protected]> wrote: > > Hi > I have a table with ~250GB per node of ~ 530 sstables per node that is > using TWCS today without TTL running cassandra 5.0.5 > I am planning to migrate the table into UCS, is it safe just to issue the > alter command in cqlsh or is it advised to do it per node via JMX and at > the end issue the cql command as was recommended to me here in the past > with earlier versions of cassandra? > > Thanks for the input > > >
