a0cf5db797
Some operators use very long group/task `shutdown_delay` settings to safely drain network connections to their workloads after service deregistration. But during incident response, they may want to cause that drain to be skipped so they can quickly shed load. Provide a `-no-shutdown-delay` flag on the `nomad alloc stop` and `nomad job stop` commands that bypasses the delay. This sets a new desired transition state on the affected allocations that the allocation/task runner will identify during pre-kill on the client. Note (as documented here) that using this flag will almost always result in failed inbound network connections for workloads as the tasks will exit before clients receive updated service discovery information and won't be gracefully drained. |
||
|---|---|---|
| .. | ||
| allocs.mdx | ||
| deployments.mdx | ||
| dispatch.mdx | ||
| eval.mdx | ||
| history.mdx | ||
| index.mdx | ||
| init.mdx | ||
| inspect.mdx | ||
| periodic-force.mdx | ||
| plan.mdx | ||
| promote.mdx | ||
| revert.mdx | ||
| run.mdx | ||
| scale.mdx | ||
| scaling-events.mdx | ||
| status.mdx | ||
| stop.mdx | ||
| validate.mdx | ||