[
https://issues.apache.org/jira/browse/CASSANDRA-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Guerrero updated CASSANDRA-21828:
-------------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values:
Consistency(12989)
Complexity: Low Hanging Fruit
Discovered By: Code Inspection
Severity: Low
Status: Open (was: Triage Needed)
> First force repair after a restart does not update the ClusterRepairTimeInSec
> auto-repair metric
> ------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-21828
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21828
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
>
> CASSANDRA-21552 ("Force repair should ignore min_repair_interval") made force
> repair skip the min_repair_interval check. As a side effect, a force repair
> that runs right after a node restart never loads the node's previous repair
> times from {{system_distributed.auto_repair_history}}. That loading only
> happened inside the interval check, which force repair now skips.
> This only affects observability, scheduling is unaffected
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
