Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-16930

Introduce Determinism (and other) Configuration Options

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 4.1-alpha1, 4.1
    • Cluster/Gossip
    • None
    • Quality Assurance
    • Low Hanging Fruit
    • All
    • None
    • Hide

      Existing unit tests, dtests and upcoming simulator

      Show
      Existing unit tests, dtests and upcoming simulator

    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.

      Attachments

        Issue Links

          Activity

            People

              benedict Benedict Elliott Smith
              benedict Benedict Elliott Smith
              Benedict Elliott Smith
              Sam Tunnicliffe
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: