You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tommy Stendahl (Jira)" <ji...@apache.org> on 2026/08/07 08:31:00 UTC
[jira] [Commented] (CASSANDRA-21552) Force repair should ignore min_repair_interval
[ https://issues.apache.org/jira/browse/CASSANDRA-21552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102702#comment-18102702 ]
Tommy Stendahl commented on CASSANDRA-21552:
--------------------------------------------
I created a PR with a patch, https://github.com/apache/cassandra/pull/5004.
> Force repair should ignore min_repair_interval
> ----------------------------------------------
>
> Key: CASSANDRA-21552
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21552
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Feature/Repair
> Reporter: Tommy Stendahl
> Assignee: Tommy Stendahl
> Priority: Normal
> Fix For: 5.0.x, 6.x, 7.x
>
>
> If you set force repair for a node the repair is not triggered until min_repair_interval has expired, this could be several hours. This seams like a mistake, if you need to do a force repair you probably want it executed ASAP regardless of min_repair_interval.
> The problem is that in AutoRepair.java, tooSoonToRunRepair() is called before myTurnToRunRepair(). Since tooSoonToRunRepair() checks if min_repair_interval has elapsed and returns early if it hasn't, a node with force_repair set is still blocked from triggering immediate repair.
--
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