[
https://issues.apache.org/jira/browse/CASSANDRA-15580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211599#comment-17211599
]
Alexander Dejanovski commented on CASSANDRA-15580:
--------------------------------------------------
I'll shepherd this ticket and start designing the test scenarios.
[~jmckenzie], regarding the use of Fallout, isn't that conversation supposed to
take place in CASSANDRA-15585? If we go down that path (and Fallout looks like
a great tool for the job), it means the reviewers and contributors need to get
up to speed with it before anything can happen. Time wise it could play against
fast completion.
My understanding also is that the OSS version of Fallout works with k8s
exclusively, which would require k8s clusters to be available from CI (just
mentioning it as I'm not sure that's something we have yet).
Also, where should these test live in the project? The natural fit for them
would be dtests (which would mean using ccm), but running tests with big nodes
could be challenging in this environment.
Was there a plan to create a new repo or just a new set of dtests?
I'd love for us to test repair on node with >= 100GB, but generating the data
could take quite some time. Using backups could make that part faster if we can
get an S3 bucket (or similar) to store the data on.
[~mck], you've been spending quite some time on the project CI lately, so your
input on what can/cannot be done there would be much appreciated.
[~marcuse] [~vinaychella], are you still willing to review the deliverables
here? What's your take on tooling and where the tests should live?
> 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: None*
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
