The rogue pending task is likely a non-issue. If your jmx command went
through without errors and you got the log message you can assume it
worked. It won't show in the schema unless you run the ALTER statement
which affects the whole cluster.
If you were switching from STCS then you wouldn't
Some more info:
- running C* 3.9
- I tried `nodetool flush` on the column family this change applies to, and
while it does seem to trigger compactions, there is still one pending that
won't seem to run
- I tried `nodetool compact` on the column family as well, with a similar
affect
Is there a way
I'm trying to change compaction strategy one node at a time. I'm using
jmxterm like this:
`echo 'set -b
org.apache.cassandra.db:type=ColumnFamilies,keyspace=my_ks,columnfamily=my_cf
CompactionParametersJson
Hi,
I need to understand whether all existing sstables are recreated/updated when
we change compaction strategy from STCS to DTCS?
Sstables are immutable by design but do we take an exception for such cases and
update same files when an Alter statement is fired to change the compaction
).
From: Anuj Wadehra
Reply-To: "user@cassandra.apache.org"
Date: Friday, January 15, 2016 at 10:16 AM
To: "user@cassandra.apache.org"
Subject: Impact of Changing Compaction Strategy
Hi,
I need to understand whether all existing sstables are recreated/updated when
we change
