Add optional jittering before any backup actions#654
Merged
m90 merged 5 commits intooffen:mainfrom Oct 17, 2025
Merged
Conversation
m90
reviewed
Oct 16, 2025
Contributor
Author
|
Done! Let me know if there is anything else to adjust. |
m90
changed the title
Member
|
This is now released in v2.45.0, thanks for your contribution! |
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.
Adds a new configuration option
BACKUP_JITTERto introduce a random delay before starting any backup actions.For context I'm backing up hundreds of containers from many servers to a single backup host with SSH on the same schedule. Handling a lot of SSH connections would be possible but would require changes I don't want either server-side or client-side. Adding a configurable startup jitter is the simplest option. I tried using hooks (
sleep $((RANDOM % $DELAY)) butpre-archiveruns after establishing the SSH connection, so it didn’t reduce the initial handshake load.