From 8c462ceff673656a3105d8036a5f554e63a4ba32 Mon Sep 17 00:00:00 2001 From: Michael Schurter Date: Fri, 17 Feb 2023 10:51:38 -0800 Subject: [PATCH] docs: clarify sysbatch supports count (#16205) Also remove old version indicators. --------- Co-authored-by: Tim Gross --- website/content/docs/schedulers.mdx | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/website/content/docs/schedulers.mdx b/website/content/docs/schedulers.mdx index 48506abcc..b403fcf14 100644 --- a/website/content/docs/schedulers.mdx +++ b/website/content/docs/schedulers.mdx @@ -52,9 +52,9 @@ should be present on every node in the cluster. Since these tasks are managed by Nomad, they can take advantage of job updating, service discovery, and more. -Since Nomad 0.9, the system scheduler will preempt eligible lower priority -tasks running on a node if there isn't enough capacity to place a system job. -See [preemption] for details on how tasks that get preempted are chosen. +The system scheduler will preempt eligible lower priority tasks running on a +node if there isn't enough capacity to place a system job. See [preemption] +for details on how tasks that get preempted are chosen. Systems jobs are intended to run until explicitly stopped either by an operator or [preemption]. If a system task exits it is considered a failure and handled @@ -62,8 +62,6 @@ according to the job's [restart] block; system jobs do not have rescheduling. ## System Batch -~> System Batch scheduling is new in Nomad 1.2. - The `sysbatch` scheduler is used to register jobs that should be run to completion on all clients that meet the job's constraints. The `sysbatch` scheduler will schedule jobs similarly to the `system` scheduler, but like a `batch` job once a @@ -82,6 +80,11 @@ Sysbatch jobs are intended to run until successful completion, explicitly stoppe by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an error are handled according to the job's [restart] block. + Like the `batch` scheduler, task groups in system batch jobs may have a `count` + greater than 1 to control how many instances are run. Instances that cannot be + immediately placed will be scheduled when resources become available, + potentially on a node that has already run another instance of the same job. + [borg]: https://research.google.com/pubs/pub43438.html [parameterized]: /nomad/docs/job-specification/parameterized [periodic]: /nomad/docs/job-specification/periodic