[
https://issues.apache.org/jira/browse/CASSANDRA-15580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224712#comment-17224712
]
Marcus Eriksson commented on CASSANDRA-15580:
---------------------------------------------
This sounds really good, thanks!
For the mixed mode tests, I think it would be fine to just write a jvm upgrade
dtest that shows that mixed-mode repair fails correctly - no need for a big
cluster to confirm this.
Regarding the inc repair tests - the "No pending repair ..." check might not be
true immediately after the repair - this is run on background compaction so it
might take a while to actually move sstables from pending -> repaired.
One thing that would be nice to include in the testing is the new
(experimental) {{-os}} flag from CASSANDRA-3200
> 4.0 quality testing: Repair
> ---------------------------
>
> Key: CASSANDRA-15580
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15580
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
> Reporter: Josh McKenzie
> Assignee: Alexander Dejanovski
> Priority: Normal
> Fix For: 4.0-rc
>
>
> Reference [doc from
> NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#]
> for context.
> *Shepherd: Alexander Dejanovski*
> We aim for 4.0 to have the first fully functioning incremental repair
> solution (CASSANDRA-9143)! Furthermore we aim to verify that all types of
> repair: (full range, sub range, incremental) function as expected as well as
> ensuring community tools such as Reaper work. CASSANDRA-3200 adds an
> experimental option to reduce the amount of data streamed during repair, we
> should write more tests and see how it works with big nodes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
