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.
85 lines
2.6 KiB
Plaintext
85 lines
2.6 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: 'Commands: job stop'
|
|
description: |
|
|
The job stop command is used to stop a running job.
|
|
---
|
|
|
|
# Command: job stop
|
|
|
|
**Alias: `nomad stop`**
|
|
|
|
The `job stop` command is used to stop a running job and signals the scheduler
|
|
to cancel all of the running allocations.
|
|
|
|
## Usage
|
|
|
|
```plaintext
|
|
nomad job stop [options] <job>
|
|
```
|
|
|
|
The `job stop` command requires a single argument, specifying the job ID or
|
|
prefix to cancel. If there is an exact match based on the provided job ID or
|
|
prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
|
|
information will be displayed.
|
|
|
|
Stop will issue a request to deregister the matched job and then invoke an
|
|
interactive monitor that exits automatically once the scheduler has processed
|
|
the request. It is safe to exit the monitor early using ctrl+c.
|
|
|
|
When ACLs are enabled, this command requires a token with the `submit-job`,
|
|
`read-job`, and `list-jobs` capabilities for the job's namespace.
|
|
|
|
## General Options
|
|
|
|
@include 'general_options.mdx'
|
|
|
|
## Stop Options
|
|
|
|
- `-detach`: Return immediately instead of entering monitor mode. After the
|
|
deregister command is submitted, a new evaluation ID is printed to the screen,
|
|
which can be used to examine the evaluation using the [eval status] command.
|
|
|
|
- `-eval-priority`: Override the priority of the evaluations produced as a result
|
|
of this job deregistration. By default, this is set to the priority of the job.
|
|
|
|
- `-verbose`: Show full information.
|
|
|
|
- `-yes`: Automatic yes to prompts.
|
|
|
|
- `-purge`: Purge is used to stop the job and purge it from the system. If not
|
|
set, the job will still be queryable and will be purged by the garbage
|
|
collector.
|
|
|
|
- `-global`
|
|
Stop a [multi-region] job in all its regions. By default, `job stop` will
|
|
stop only a single region at a time. Ignored for single-region jobs.
|
|
|
|
- `-no-shutdown-delay`
|
|
Ignore the the group and task [`shutdown_delay`] configuration so that
|
|
there is no delay between service deregistration and task
|
|
shutdown. Note that using this flag will result in failed network
|
|
connections to the allocations being stopped.
|
|
|
|
## Examples
|
|
|
|
Stop the job with ID "job1":
|
|
|
|
```shell-session
|
|
$ nomad job stop job1
|
|
==> Monitoring evaluation "43bfe672"
|
|
Evaluation status changed: "pending" -> "complete"
|
|
==> Evaluation "43bfe672" finished with status "complete"
|
|
```
|
|
|
|
Stop the job with ID "job1" and return immediately:
|
|
|
|
```shell-session
|
|
$ nomad job stop -detach job1
|
|
507d26cb
|
|
```
|
|
|
|
[eval status]: /docs/commands/eval-status
|
|
[multi-region]: /docs/job-specification/multiregion
|
|
[`shutdown_delay`]: /docs/job-specification/group#shutdown_delay
|