You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2020/07/24 17:16:00 UTC

[jira] [Commented] (CASSANDRA-15580) 4.0 quality testing: Repair

    [ https://issues.apache.org/jira/browse/CASSANDRA-15580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164551#comment-17164551 ] 

Caleb Rackliffe commented on CASSANDRA-15580:
---------------------------------------------

I was talking w/ [~jasonstack] on CASSANDRA-15665, and it might be useful to have some basic testing around the fact that we don't allow STREAMING connections between 3.x and 4.0 nodes.

CC [~jmeredithco]

> 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
>            Reporter: Josh McKenzie
>            Assignee: Benjamin Lerer
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> Reference [doc from NGCC|https://docs.google.com/document/d/1uhUOp7wpE9ZXNDgxoCZHejHt5SO4Qw1dArZqqsJccyQ/edit#] for context.
> *Shepherd: Blake Eggleston*
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org