Skip to content
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

docs: improve cross-links for scheduler preemption #25203

Merged
merged 1 commit into from
Feb 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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