Repository navigation
Conversation
With the deployment of the "kickd" varlink based backchannel to trigger updates by the ACP we no longer need the extremly aggressive 2min update timer. Instead this commit moves to a more reasonable 8h with a 30min spread. As side effect of the spread is that on boot the first update is also only checked after the spread. That is okay for now but we should have a mode that checks for updates first thing (even before servics come up) eventually. ENG-100
Member
Author
|
Closing for now as this is not ready. |
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
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.
It seems we need to reopen this via https://github.com/amutable/quarry/compare/normal-udpate-timer?expand=1 as a closed PR that got force pushed to can't be reopened(?)
Polling for updates every 2 minutes is far too aggressive. This commit moves the timer to a more reasonable 8h interval with a 30min random spread.
As a side effect of the spread, the first check after boot also only happens after the spread. That is okay for now, but eventually we should have a mode that checks for updates first thing (even before services come up).