Leader election: do not wait 2 hours for retry, even in dev mode #232
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.
I found it useful to leverage the
CATTLE_DEV_MODE
environment variable in order to make leader leases last longer - this is pretty much needed when attaching a debugger (eg. via delve) - else the process is automatically killed after some seconds.Problem with
CATTLE_DEV_MODE
in that scenario is, at the moment, that it also elongates the retry period, which means the initial leader election at process start will also take two hours, which is a bit impractical.This PR tries to address the issue by elongating all times but the retry period - I tested it manually and it works great for delve debugging.
Related: #234
Issue: rancher/rancher#39506