Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-1.25] Add jitter to scheduled snapshots and retry harder on conflicts #6782

Merged
merged 1 commit into from
Jan 26, 2023

Conversation

brandond
Copy link
Member

Proposed Changes

Add jitter to scheduled snapshots and retry harder on conflicts

Also ensure that the snapshot job does not attempt to trigger multiple concurrent runs, as this is not supported.

Types of Changes

bugfix

Verification

See linked issue

Testing

Linked Issues

User-Facing Change

Scheduled etcd snapshots are now offset by a short random delay of up to several seconds. This should prevent multi-server clusters from executing pathological behavior when attempting to simultaneously update the snapshot list ConfigMap. The snapshot controller will also be more persistent in attempting to update the snapshot list.

Further Comments

Also ensure that the snapshot job does not attempt to trigger multiple concurrent runs, as this is not supported.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
@brandond brandond requested a review from a team as a code owner January 19, 2023 20:50
@brandond brandond merged commit 6344590 into k3s-io:release-1.25 Jan 26, 2023
@brandond brandond deleted the cron_jitter_release-1.25 branch June 6, 2024 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants