From 937d0b0e8a42de161e71943524c162b189b38edd Mon Sep 17 00:00:00 2001 From: Tim Gross Date: Tue, 25 Feb 2025 13:56:54 +0000 Subject: [PATCH] backport of commit 7997a760dffc0c2a32eb26f566b2eb3875554d1d --- website/content/docs/concepts/scheduling/preemption.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/website/content/docs/concepts/scheduling/preemption.mdx b/website/content/docs/concepts/scheduling/preemption.mdx index 93ce9723a6e..faaa5518b07 100644 --- a/website/content/docs/concepts/scheduling/preemption.mdx +++ b/website/content/docs/concepts/scheduling/preemption.mdx @@ -23,7 +23,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 @@ -88,3 +91,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