[
https://issues.apache.org/jira/browse/CASSANDRA-15580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214619#comment-17214619
]
Josh McKenzie commented on CASSANDRA-15580:
-------------------------------------------
Great points about the current mismatch of infra (k8s vs. else) fallout brings
to the table. Agreed we shouldn't delay 4.0 on bringing that infra up to speed.
There's a few other new testing frameworks that are falling into the "do
one-off or point testing instead of coupling 4.0 GA to wiring these up in
CI/CD" as well.
Would have to dig into the code to answer the question about the specificity on
targeting latest on mixed version cluster repair. trunk and previous major is
probably quite fine.
IMO, what you've enumerated above is a respectable set of new coverage for us
to wire up that should hit the big targets we have and reduce our uncertainty
in the process.
> 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]
