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

Set longer default retry, backoff and attempt count for Consul Template #13020

Closed
mikenomitch opened this issue May 13, 2022 · 1 comment · Fixed by #13041
Closed

Set longer default retry, backoff and attempt count for Consul Template #13020

mikenomitch opened this issue May 13, 2022 · 1 comment · Fixed by #13041

Comments

@mikenomitch
Copy link
Contributor

mikenomitch commented May 13, 2022

Proposal

If a user does not override retry attempts, max backoff, or default backoff values on Consul Template, they get only 12 retry attempts and only a few minutes of retry time before tasks start failing (See #13019 for a failure issue). This means that if Vault or Consul goes down for over a few minutes (or a connection is bad) then all tasks on the Nomad cluster can go down.

We should default these times to greater numbers to they have more protection in the case of long outages.

This should be done for both consul and vault.

Use-cases

This would allow Nomad tasks to be more resilient if Vault or Consul go down.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants