[CASSANDRA-16930] Introduce Determinism (and other) Configuration Options

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1-alpha1, 4.1
• Component/s: Cluster/Gossip
• Change Category: Quality Assurance
• Complexity: Low Hanging Fruit
• Platform: All

Source Control Link

fe9cff663b48fecdb964caaded2004e83a0c89f4

Test and Documentation Plan

Existing unit tests, dtests and upcoming simulator

• Assignee: Benedict Elliott Smith
• Reporter: Benedict Elliott Smith

Authors

Benedict Elliott Smith

Reviewers

Sam Tunnicliffe

• Created: 08/Sep/21 17:52
• Updated: 06/Apr/23 11:38
• Resolved: 07/Oct/21 15:32

Description

In order to support CEP-10 we must enable deterministic execution within Cassandra, support disabling certain optional features that are incompatible with simulation, and support overriding some existing features.

Some determinism will be enabled by the Simulator itself, but there are aspects of Cassandra that must be made compliant as well. This includes: compression system-wide, memtable overhead computation, specifying the number of processors used for computation/decisions, specifing all cache sizes explicitly, enabling deterministic table IDs, and supporting deterministic node IDs for TimeUUID creation.

We also want to be able disable sstable activity tracking, and to be able to happily ignore problems with native filesystem methods and SIGAR. We also want to be able to override the migration delay, batch sync interval and system auth replication factor.

For pluggability we also want to be able to specify a custom FailureDetector.

Issue Links

• causes: CASSANDRA-17782 `DatabaseDescriptor#clientInitialization` should set the `newFailureDetector` (maybe to a NoOpFailureDetector?)
• causes: CASSANDRA-18393 Flaky test: org.apache.cassandra.cql3.validation.operations.InsertUpdateIfConditionTest.testConditionalUpdate[1: clusterMinVersion=3.11]-compression.jdk1.8 on trunk
• is a child of: CASSANDRA-16929 CEP-10: General Improvements (Phase 2)