Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
CASSANDRA-8177 sequential repair is much more expensive than parallel repair
- Resolved
-
CASSANDRA-8641 Repair causes a large number of tiny SSTables
- Resolved
-
CASSANDRA-7655 Slow repair on empty cluster
- Resolved
- relates to
-
CASSANDRA-6455 Improve concurrency of repair process
- Resolved
- supercedes
-
CASSANDRA-9491 Inefficient sequential repairs against vnode clusters
- Open