[ 
https://issues.apache.org/jira/browse/CASSANDRA-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709342#comment-17709342
 ] 

Andres de la Peña edited comment on CASSANDRA-16930 at 4/6/23 11:38 AM:
------------------------------------------------------------------------

Bisection points to the commit for this ticket as the first one introducing the 
test failures of {{InsertUpdateIfConditionTest}} and 
{{InsertUpdateIfConditionCollectionsTest}} reported by CASSANDRA-18393:
 * Before: 
[commit|https://github.com/apache/cassandra/commit/ce2a0a28bc9ca21e1fae29f2a38448a877db06c3]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2807/workflows/e08f482a-40bd-4dfc-b322-353572717ada]
 * After: 
[commit|https://github.com/apache/cassandra/commit/fe9cff663b48fecdb964caaded2004e83a0c89f4]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2808/workflows/a63798dd-1916-4ef6-9e4c-9962127fc66b]

CASSANDRA-18393 added a fix for those tests, but it seems that they are still 
flaky in a different way, as reported by CASSANDRA-18393:
 * Before: 
[commit|https://github.com/apache/cassandra/commit/89f3978dcde958fbad191b8cf628fd89ace64d7a]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2803/workflows/dc769b19-b383-4332-92db-12e7e54a49fa]
 * After: 
[commit|https://github.com/apache/cassandra/commit/cc28e1a85e2e5760436030ca57667fa69d6de233]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2804/workflows/5bec4990-05da-4879-b097-57116c30ba5b]


was (Author: adelapena):
Bisections points to the commit for this ticket as the first one introducing 
the test failures of {{InsertUpdateIfConditionTest}} and 
{{InsertUpdateIfConditionCollectionsTest}} reported by CASSANDRA-18393:
 * Before: 
[commit|https://github.com/apache/cassandra/commit/ce2a0a28bc9ca21e1fae29f2a38448a877db06c3]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2807/workflows/e08f482a-40bd-4dfc-b322-353572717ada]
 * After: 
[commit|https://github.com/apache/cassandra/commit/fe9cff663b48fecdb964caaded2004e83a0c89f4]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2808/workflows/a63798dd-1916-4ef6-9e4c-9962127fc66b]

CASSANDRA-18393 added a fix for those tests, but it seems that they are still 
flaky in a different way, as reported by CASSANDRA-18393:
 * Before: 
[commit|https://github.com/apache/cassandra/commit/89f3978dcde958fbad191b8cf628fd89ace64d7a]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2803/workflows/dc769b19-b383-4332-92db-12e7e54a49fa]
 * After: 
[commit|https://github.com/apache/cassandra/commit/cc28e1a85e2e5760436030ca57667fa69d6de233]
 
[CI|https://app.circleci.com/pipelines/github/adelapena/cassandra/2804/workflows/5bec4990-05da-4879-b097-57116c30ba5b]

> 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.1-alpha1, 4.1
>
>
> 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.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to