[
https://issues.apache.org/jira/browse/CASSANDRA-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072667#comment-18072667
]
Isaac Reath commented on CASSANDRA-21247:
-----------------------------------------
ML Thread: https://lists.apache.org/thread/z3mdvw78f5cqovq781tvjm537w66cpsm
There was some good feedback from [~clohfink] on how they are using this
guardrail.
CASSANDRA-21290 was merged to address point 1 that he laid out and
CASSANDRA-21293 was created for point two. For point 3, I can create a follow
up JIRA to add some documentation when the ongoing discussion on the ML around
redoing the docs has settled (i.e.
https://lists.apache.org/thread/wzh5cnnp27o2w5jtg3xt4l1vmj9fv8ts).
> Enable check_data_resurrection by default in cassandra_latest.yaml
> ------------------------------------------------------------------
>
> Key: CASSANDRA-21247
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21247
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
> Reporter: Isaac Reath
> Assignee: Isaac Reath
> Priority: Normal
> Fix For: 6.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The check_data_resurrection configuration was added to 4.1 in CASSANDRA-17180
> to prevent nodes from starting up if a node has been offline longer than the
> minimum gc_grace_seconds. While this feature is critical for ensuring that we
> don't resurrect data, there are members of the community who may not know
> that it was added (CASSANDRA-21221 for example).
> This ticket proposes enabling this setting by default in
> cassandra_latest.yaml so that users who take the most recent production
> settings from this file are able to automatically benefit from this feature
> in the next major release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
