Re: Cassandra 4.0 upgrade - Upgradesstables

Though it is not required to run upgradesstables, but upgradesstables -a will re-write the file to kick out tombstones, in sizeTieredcompaction, the largest files may stay a long time to wait for the next compaction to kick out tombstones. So it really depends, to run it or not, usually upgrades

Re: Cassandra 4.0 upgrade - Upgradesstables

Thank you On Tue, Aug 16, 2022 at 11:48 AM C. Scott Andreas wrote: > No downside at all for 3.x -> 4.x (however, Cassandra 3.x reading 2.1 > SSTables incurred a performance hit). > > Many users of Cassandra don't run upgradesstables after 3.x -> 4.x > upgrades at all. It's not necessary to run

Re: Cassandra 4.0 upgrade - Upgradesstables

No downside at all for 3.x -> 4.x (however, Cassandra 3.x reading 2.1 SSTables incurred a performance hit).Many users of Cassandra don't run upgradesstables after 3.x -> 4.x upgrades at all. It's not necessary to run until a hypothetical future time if/when support for reading Cassandra 3.x

Re: Cassandra 4.0 upgrade - Upgradesstables

Thank you Erick, > it is going to be single-threaded by default so it will take a while to get through all the sstables on dense nodes Is there any downside if the upgradesstables take longer (example 1-2 days), other than I/O? Also when is the upgradesstable get triggered? after every node is

Re: Cassandra 4.0 upgrade - Upgradesstables

As convenient as it is, there are a few caveats and it isn't a silver bullet. The automatic feature will only kick in if there are no other compactions scheduled. Also, it is going to be single-threaded by default so it will take a while to get through all the sstables on dense nodes. In

Cassandra 4.0 upgrade - Upgradesstables

Hello, I am evaluating the upgrade from 3.11.x to 4.0.x and as per CASSANDRA-14197 we don't need to run upgradesstables any more. We have tested this in a test environment and see that setting "-Dcassandra.automatic_sstable_upgrade=true"