You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict Elliott Smith (Jira)" <ji...@apache.org> on 2021/09/28 10:47:00 UTC

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict Elliott Smith updated CASSANDRA-16930:
-----------------------------------------------
    Change Category: Quality Assurance
         Complexity: Low Hanging Fruit
        Component/s: Cluster/Gossip
      Fix Version/s: 4.x
          Reviewers: Sam Tunnicliffe
           Assignee: Benedict Elliott Smith
             Status: Open  (was: Triage Needed)

> Introduce Determinism (and other) Configuration Options
> -------------------------------------------------------
>
>                 Key: CASSANDRA-16930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16930
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Gossip
>            Reporter: Benedict Elliott Smith
>            Assignee: Benedict Elliott Smith
>            Priority: Normal
>             Fix For: 4.x
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org