mirror of
https://github.com/kemko/nomad.git
synced 2026-01-07 19:05:42 +03:00
Apply suggestions from code review
Co-Authored-By: preetapan <preetha@hashicorp.com>
This commit is contained in:
@@ -420,5 +420,5 @@ The table below shows this endpoint's support for
|
||||
```
|
||||
|
||||
- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
|
||||
- `SystemSchedulerEnabled`(bool:true) - Specifies whether preemption for system jobs is enabled. Note that
|
||||
if this is set to true, then system jobs can preempt any other jobs.
|
||||
- `SystemSchedulerEnabled` (`bool`: `true`) - Specifies whether preemption for system jobs is enabled. Note that
|
||||
if this is set to true, then system jobs can preempt any other jobs.
|
||||
|
||||
@@ -38,7 +38,7 @@ Preemption is enabled by default in Nomad 0.9. Operators can use the [scheduler
|
||||
|
||||
Nomad uses the [job priority](/docs/job-specification/job.html#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
|
||||
delta of more than 10 from the job needing placement are chosen.
|
||||
delta of more than 10 from the job needing placement are eligible for preemption.
|
||||
|
||||
For example, consider a node with the following distribution of allocations:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user