From 9347613d9ae182845db7d88b36388dde8202f2c0 Mon Sep 17 00:00:00 2001 From: Michael Schurter Date: Wed, 11 May 2022 17:06:17 -0700 Subject: [PATCH] docs: add `sysbatch` to scheduling internals (#12954) --- website/content/docs/internals/scheduling/scheduling.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/internals/scheduling/scheduling.mdx b/website/content/docs/internals/scheduling/scheduling.mdx index c62d532f1..9c07454ff 100644 --- a/website/content/docs/internals/scheduling/scheduling.mdx +++ b/website/content/docs/internals/scheduling/scheduling.mdx @@ -39,9 +39,9 @@ Nomad servers run scheduling workers, defaulting to one per CPU core, which are used to process evaluations. The workers dequeue evaluations from the broker, and then invoke the appropriate scheduler as specified by the job. Nomad ships with a `service` scheduler that optimizes for long-lived services, a `batch` -scheduler that is used for fast placement of batch jobs, a `system` scheduler -that is used to run jobs on every node, and a `core` scheduler which is used -for internal maintenance. +scheduler that is used for fast placement of batch jobs, `system` and +`sysbatch` schedulers that are used to run jobs on every node, and a `core` +scheduler which is used for internal maintenance. Schedulers are responsible for processing an evaluation and generating an allocation _plan_. The plan is the set of allocations to evict, update, or