Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Operability
-
Normal
-
All
-
None
-
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.
Attachments
Attachments
Issue Links
- causes
-
CASSANDRA-18046 A few large DTests failing on trunk after CASSANDRA-17679
- Resolved
- is duplicated by
-
CASSANDRA-18046 A few large DTests failing on trunk after CASSANDRA-17679
- Resolved
- is related to
-
CASSANDRA-16290 Consistency can be violated when bootstrap or decommission is resumed after node restart
- Open
-
CASSANDRA-15264 Make resumable bootstrap off by default
- Resolved