I made changes to gc_grace_seconds in my local Cassandra nodes.
When upgrading from 10.2.10 to 10.3 CU5 this setting got changed again.
I assumed this was due to RN: Cassandra: gc_grace_seconds will now be set to 1 day by default and to 4 hours for records with TTL set [ID_34763]
However, on another system when going from 10.3 CU3 to CU4, my gc_grace_seconds remained untouched.
Is the gc_grace_seconds setting only changed when performing a main release upgrade, not when performing a CU update?
Hi Robin,
That action should not be tied to crossing a specific version, the change should happen from 10.3CU4 every time the DMA starts up. The DMA should log the attempt (and issues) in SLDBConnection.txt. The keywords to look for will be gc_grace_seconds or gc grace seconds.
Are there other differences between the setup? I.e. cassandra version, SingleNode vs CassandraCluster,...?