luxolus/open-nomad
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

docs: clarify sysbatch supports count (#16205)

Browse source 
Also remove old version indicators.

---------

Co-authored-by: Tim Gross <tgross@hashicorp.com>
This commit is contained in:
Michael Schurter 2023-02-17 10:51:38 -08:00 committed by GitHub
parent 8295d0e516
commit f13f022176
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
website/content/docs/schedulers.mdx
View file

@ -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