From ffddd697c4edc506a79d0dd72c906ff58ae90569 Mon Sep 17 00:00:00 2001 From: Yishan Lin Date: Fri, 17 Apr 2020 09:34:07 -0700 Subject: [PATCH] docs: update preemption page This page has not been updated (yet) to reflect that support for all 3 job types (service, batch, system) which shipped in 0.9.2. The current page implies that preemption is only available for system jobs. This is early preparation for Nomad 0.12, where we plan to move Preemption from Enterprise feature suite to OSS for all. --- website/pages/docs/internals/scheduling/preemption.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/docs/internals/scheduling/preemption.mdx b/website/pages/docs/internals/scheduling/preemption.mdx index 8651a234b..8300731be 100644 --- a/website/pages/docs/internals/scheduling/preemption.mdx +++ b/website/pages/docs/internals/scheduling/preemption.mdx @@ -25,7 +25,7 @@ Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result f job remain in the pending state until sufficient resources become available - regardless of the defined priority. This leads to priority inversion, where a low priority task can prevent high priority tasks from completing. -Nomad 0.9 brings preemption capabilities to system jobs. The Nomad scheduler will evict lower priority running allocations +Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back into the plan queue.