Skip to content

Commit

Permalink
docs: improve cross-links for scheduler preemption
Browse files Browse the repository at this point in the history
Fix a broken link from the preemption concepts docs to the relevant API. Also
include a link to the relevant command.

Ref: #25038
  • Loading branch information
tgross committed Feb 24, 2025
1 parent cee1135 commit 0ecca63
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion website/content/docs/concepts/scheduling/preemption.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,10 @@ into the plan queue.

## Details

Preemption is enabled by default for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
Preemption is enabled by default for system jobs. You can use the [scheduler
config][sched-config-api] API endpoint or [`nomad operator scheduler
set-config`][sched-config-cli] commands to disable preemption or enable it for
other job types.

Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
Expand Down Expand Up @@ -95,3 +98,5 @@ They provide the operator a sample of the type of allocations that could be pree
[borg]: https://research.google.com/pubs/pub43438.html
[img-data-model]: /img/nomad-data-model.png
[img-eval-flow]: /img/nomad-evaluation-flow.png
[sched-config-api]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
[sched-config-cli]: /nomad/docs/commands/operator/scheduler/set-config

0 comments on commit 0ecca63

Please sign in to comment.