[CASSANDRA-5220] Repair improvements when using vnodes

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0 beta 1
• Labels: performance repair
• Assignee: Marcus Olsson
• Reporter: Brandon Williams

Authors

Marcus Olsson

Reviewers

Stefania Alborghetti

• Created: 04/Feb/13 23:13
• Updated: 16/Apr/19 09:32
• Resolved: 11/Aug/15 13:36

Description

Currently when using vnodes, repair takes much longer to complete than without them. This appears at least in part because it's using a session per range and processing them sequentially. This generates a lot of log spam with vnodes, and while being gentler and lighter on hard disk deployments, ssd-based deployments would often prefer that repair be as fast as possible.

Issue Links

• is duplicated by: CASSANDRA-8177 sequential repair is much more expensive than parallel repair
• is duplicated by: CASSANDRA-8641 Repair causes a large number of tiny SSTables
• is duplicated by: CASSANDRA-7655 Slow repair on empty cluster
• relates to: CASSANDRA-6455 Improve concurrency of repair process
• supercedes: CASSANDRA-9491 Inefficient sequential repairs against vnode clusters