CASSANDRA-21247: [6.0] Enable check_data_resurrection by default in cassandra_latest.yaml#4762
Conversation
…ra_latest.yaml This patch updates the default value for check_data_resurrection so that users can benefit from this feature automatically in the next major release. patch by Isaac Reath; reviewed by TBD for CASSANDRA-21247
isaacreath
force-pushed
the
CASSANDRA-21247-cassandra-6.0
branch
from
1d778b3 to
6c92219
Compare
| # # Minimum grace period for the check, defaults to 0. Useful when gc_grace_seconds is very | ||
| # # small (e.g. 0) to avoid blocking startup immediately. | ||
| # minimum_threshold: 3h | ||
| minimum_threshold: 3h |
There was a problem hiding this comment.
As I mentioned in the other PR, did we discuss regarding this 3h default value in dev community, as this will impact all upgrading clusters?
There was a problem hiding this comment.
@skoppu22 this is cassandra_latest.yaml, not cassandra.yaml. If somebody upgrades they will upgrade to cassandra.yaml where it is turned off.
We do not have any real guarantees in cassandra_latest.yaml. It is suitable just for having latest stuff and "recommended settings" which can people start to use for their new clusters or for the evaluation of this tech as such, but we never established that a user can upgrade from one cassandra_latest.yaml to the other and expect it all to just work. You get these guarantees in cassandra.yaml instead.
3 participants
From discussion on https://issues.apache.org/jira/browse/CASSANDRA-21221, it was clear that users may not know that this feature exists. This PR updates the cassandra_latest.yaml so that users who take advantage of the recommended production settings can get this feature automatically in the next release.