[CASSANDRA-9109] Repair appears to have some of untested behaviors

• Type: Improvement
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Consistency/Repair, Legacy/Testing
• Assignee: Unassigned
• Reporter: Ariel Weisberg
• Created: 02/Apr/15 22:52
• Updated: 16/Apr/19 09:31

Description

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.

Issue Links

• Is contained by: CASSANDRA-9012 Triage missing test coverage
• relates to: CASSANDRA-8316 "Did not get positive replies from all endpoints" error on incremental repair
• relates to: CASSANDRA-8366 Repair grows data on nodes, causes load to become unbalanced