You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 05:51:00 UTC

[jira] [Updated] (CASSANDRA-9109) Repair appears to have some of untested behaviors

     [ https://issues.apache.org/jira/browse/CASSANDRA-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

C. Scott Andreas updated CASSANDRA-9109:
----------------------------------------
    Component/s: Repair

> Repair appears to have some of untested behaviors
> -------------------------------------------------
>
>                 Key: CASSANDRA-9109
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9109
>             Project: Cassandra
>          Issue Type: Test
>          Components: Repair, Testing
>            Reporter: Ariel Weisberg
>            Priority: Major
>
> There is AntiCompactionTest and a few single process unit tests, but they aren't very convincing. Looking at the docs to nodetool it looks like there are a few different ways that repair could operate that aren't explored. dtest wise there is repair_test and incremental_repair test which do give some useful coverage, but don't do everything.
> It's also the kind of thing you might like to see tested with some concurrent load to catch interactions with everything else moving about, but a dtest may not be the right place to do that.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org