kvserver: warn more aggressively about slow AddSST apply #80160
Merged
Conversation
This file contains 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
AddSST application is "just" a hard-link on any kind of reasonable file system, so it shouldn't take north of 30s ever. Anecdotally, during a recent spat of experiments, I never saw this logging fire despite raft handling cycles taking upward of 450s. So this is almost certainly too conservative. Change the timeout to a 500ms cutoff, which matches the "slow raft ready" message. Release note: None
|
This change is |
erikgrinaker
approved these changes
Apr 19, 2022
|
bors r=erikgrinaker |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
AddSST application is "just" a hard-link on any kind of reasonable file system,
so it shouldn't take north of 30s ever. Anecdotally, during a recent spat of
experiments, I never saw this logging fire despite raft handling cycles taking
upward of 450s. So this is almost certainly too conservative.
Change the timeout to a 500ms cutoff, which matches the "slow raft ready"
message.
Release note: None