-
Notifications
You must be signed in to change notification settings - Fork 881
fix(coderd): extract provisionerdserver.StaleInterval to 90 seconds #15643
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is an improvement, but I still find this approach lacking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the change 👍🏻, if we noticed that the decreased interval leads to too many false-positive stale states, then we can consider raising it to 150s or something like that.
|
||
// StaleInterval is the amount of time after the last heartbeat for which | ||
// the provisioner will be reported as 'stale'. | ||
StaleInterval = 90 * time.Second |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I configure my heartbeat interval to be greater than 90 sec, it reads like this will introduce false negatives where a heartbeat simply hasn't run but the provisioner presents as stale. Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, but we don't expose that as a coderd
configuration knob yet. The only way you could configure that is by editing the source code right now.
Follow-up from #15578
Extracts
provisionerdserver.StaleInterval
and sets it to 90 seconds by default