[
https://issues.apache.org/jira/browse/CASSANDRA-15580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224834#comment-17224834
]
Alexander Dejanovski commented on CASSANDRA-15580:
--------------------------------------------------
Thanks for the feedback [~marcuse] and [~jmckenzie]!
Good point for using in jvm upgrade dtests for testing mixed version repairs
(y) I'll create a subticket for this.
I'll add the flag from CASSANDRA-3200 to the test plan for sure, but need to
think a little bit about what to test precisely in this scenario.
We'd need to figure out the following things:
* How/where do we provision the nodes?
AFAIK we don't have a test suite such as the one we're planning to build here
which will require to spin up actual clusters on external VMs (no ccm).
Spinning up AWS instances is a low friction path with a tool such as
tlp-cluster (we'll need a sponsor for hosting the instances).
k8s is probably down the path but it could be good to have the community
operator before we use it.
Are there any other obvious tools/ways to spin up multi instances clusters?
* Which testing framework to use?
I personally like using Gherkin syntax based frameworks such as Cucumber, but
we'd need to get a feel for the community's appetite to introduce such a
framework.
Otherwise we'd probably fallback to JUnit but my take on this is that while
it's really good for unit tests, it's no fit for integration tests.
Any input/opinion on testing framework is appreciated.
* Where is that test suite stored?
It would be good to have it stored directly in the Cassandra repo but we could
store it in a side project like it was done for dtests.
> 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]
