cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-16262) 4.0 Quality: Coordination & Replication Fuzz Testing
Date Thu, 15 Jul 2021 07:31:00 GMT


ASF GitHub Bot updated CASSANDRA-16262:
    Labels: pull-request-available  (was: )

> 4.0 Quality: Coordination & Replication Fuzz Testing
> ----------------------------------------------------
>                 Key: CASSANDRA-16262
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/fuzz
>            Reporter: Caleb Rackliffe
>            Assignee: Alex Petrov
>            Priority: Normal
>              Labels: pull-request-available
>             Fix For: 4.x
> CASSANDRA-16180, CASSANDRA-16181, and CASSANDRA-15977 have largely focused on auditing
the existing tests around coordination, replication, and read-repair, respectively. We've
expanded existing test cases, added coverage around components that we've refactored along
the way, and added in-JVM dtest upgrade tests where possible.
> What remains is verifying the distributed read and write paths in the face of common
operational events, namely node restarts, bootstrapping, decommission, and cleanup. If we
can find a way to simulate these events, [Harry|]
seems like a good candidate to host the verification logic itself.
> To keep things simple initially, I would propose that we start by testing simple read-only
and write-only workloads (the former without read repair).

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message