[jira] [Created] (CASSANDRA-20180) AutoRepair scheduler should attempt to avoid selecting nodes when their replicas are already scheduling repairs

["Andy Tolbert (Jira)" <ji...@apache.org>]

Andy Tolbert created CASSANDRA-20180:
----------------------------------------

             Summary: AutoRepair scheduler should attempt to avoid selecting nodes when their replicas are already scheduling repairs
                 Key: CASSANDRA-20180
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20180
             Project: Apache Cassandra
          Issue Type: Improvement
            Reporter: Andy Tolbert


Currently AutoRepair scheduling does not factor in whether replicas of a node are running their auto repair schedule.

Ideally, the scheduler would attempt to have repairs issued in a replica disjoint way if it is possible.

 e.g. assume you have nodes 1, 2, 3, 4, ..., 12  and replication is in sequential order with RF 3
e.g. 5 shares ranges with 3, 4, 6, 7

If 5 has an ongoing repair, we could avoid having nodes 3, 4, 6, 7 as being chosen in favor of other nodes.

Anecdotally, I had a 12 node cluster with {{parallel_repair_count}} of 3, and I observed that at a given time, 3 replicas of one another were scheduling incremental repairs, which could lead to conflicts if ranges overlap sstables.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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