-
Notifications
You must be signed in to change notification settings - Fork 114
nomad: clarify lost_after default and fix conflicting statements #1460
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
base: nomad/1.11.1
Are you sure you want to change the base?
Conversation
…d fix conflicting statements
| disconnected. | ||
|
|
||
| - `stop_on_client_after` `(string: "")` - Specifies a duration after which a | ||
| disconnected Nomad client will stop its allocations. Setting |
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.
Removing this because it implies these two settings can be set at the same time, however they cannot, and that is mentioned in several places in the docs.
Vercel Previews Deployed
|
Broken Link CheckerNo broken links found! 🎉 |
| [drain]: /nomad/commands/node/drain | ||
| [deadline]: /nomad/commands/node/drain#deadline | ||
| [replaces]: /nomad/docs/job-specification/disconnect#replace | ||
| [replaces]: /nomad/docs/job-specification/disconnect |
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.
Linking to the replace parameter was misleading, so instead, just link to the disconnect overview.
Please go to the
Previewtab and select the appropriate template:Terraform
Currently in Draft until hashicorp/nomad#27053 is reviewed, which fixes some disconnect.lost_after and disconnect.replace behavior.