Open
Description
The idea for such kind of test comes from Michal here.
Quoting this comment here as well:
In general, tablet migration can happen at anytime and it could make SM skip some tablets when performing repair.
SM should stop tablet migration when performing repair and resume it afterwards.
This gives an idea for additional test scenario:
- validate that tablet migration is on (how to do it?)
- run repair on tablet tables (no vnode tables so that it's easier to test)
- validate that tablet migration is off
- pause repair it in the middle
- validate that tablet migration is on
- make something to cause tablet migration (perhaps modifying initial_tablets keyspace/table option would work)
- resume repair
- validate that tablet migration if off
- repair finishes
- validate that tablet migration is on
- validate that all data have been repaired (how to do it?)