You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: