Fix resync/repair ticker period - #3154
Open
baarde wants to merge 1 commit into
Open
Conversation
baarde
requested review from
FxKu,
idanovinda,
jopadi and
mikkeloscar
as code owners
July 31, 2026 14:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello,
This is a fix for #2321.
#304 introduced a
repair_period(5 minutes) that is smaller thanresync_period(30 minutes) to fix failing clusters.However, the resync/repair ticker's period is currently set to the
resync_period, so having a shorterrepair_periodhas no effect.This PR sets the ticker's period to the smallest value.