[
https://issues.apache.org/jira/browse/CASSANDRA-16262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-16262:
----------------------------------------
Description:
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|https://github.com/apache/cassandra-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).
was:
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, and
decommission. If we can find a way to simulate these events,
[Harry|https://github.com/apache/cassandra-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).
> 4.0 Quality: Coordination & Replication Fuzz Testing
> ----------------------------------------------------
>
> Key: CASSANDRA-16262
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16262
> Project: Cassandra
> Issue Type: Task
> Components: Test/fuzz
> Reporter: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.0-rc
>
>
> 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|https://github.com/apache/cassandra-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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
