[CASSANDRA-17679] Make resumable bootstrap feature optional

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Consistency/Streaming
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=39a470235af13837a1a022ab0a1b6f8f062bcf6a

Test and Documentation Plan

New unit testing

• Assignee: Josh McKenzie
• Reporter: Josh McKenzie

Authors

Josh McKenzie

Reviewers

Marcus Eriksson

• Created: 02/Jun/22 20:22
• Updated: 12/Sep/23 13:02
• Resolved: 28/Oct/22 18:49

Description

From the patch I'm working on:

# In certain environments, operators may want to disable resumable bootstrap in order to avoid potential correctness
# violations or data loss scenarios. Largely this centers around nodes going down during bootstrap, tombstones being
# written, and potential races with repair. By default we leave this on as it's been enabled for quite some time,
# however the option to disable it is more palatable now that we have zero copy streaming as that greatly accelerates
# bootstraps. This defaults to true.
# resumable_bootstrap_enabled: true

Not really a great fit for guardrails as it's less a "feature to be toggled on and off" and more a subset of a specific feature that in certain circumstances can lead to issues.

Issue Links

• causes: CASSANDRA-18046 A few large DTests failing on trunk after CASSANDRA-17679
• is duplicated by: CASSANDRA-18046 A few large DTests failing on trunk after CASSANDRA-17679
• is related to: CASSANDRA-16290 Consistency can be violated when bootstrap or decommission is resumed after node restart
• is related to: CASSANDRA-15264 Make resumable bootstrap off by default