mirror of
https://github.com/kemko/nomad.git
synced 2026-01-05 01:45:44 +03:00
Merge branch 'master' of https://github.com/hashicorp/nomad
This commit is contained in:
@@ -75,8 +75,8 @@ and density of applications, but is also augmented by affinity and anti-affinity
|
||||
Once the scheduler has ranked enough nodes, the highest ranking node is selected and
|
||||
added to the allocation plan.
|
||||
|
||||
When planning is complete, the scheduler submits the plan to the leader and
|
||||
gets added to the plan queue. The plan queue manages pending plans, provides priority
|
||||
When planning is complete, the scheduler submits the plan to the leader which adds
|
||||
the plan to the plan queue. The plan queue manages pending plans, provides priority
|
||||
ordering, and allows Nomad to handle concurrency races. Multiple schedulers are running
|
||||
in parallel without locking or reservations, making Nomad optimistically concurrent.
|
||||
As a result, schedulers might overlap work on the same node and cause resource
|
||||
|
||||
@@ -9,8 +9,7 @@ description: |-
|
||||
# Job Specification
|
||||
|
||||
Jobs can be specified either in [HCL](https://github.com/hashicorp/hcl) or JSON.
|
||||
HCL is meant to strike a balance between human readable and editable, as well
|
||||
as being machine-friendly.
|
||||
HCL is meant to strike a balance between human readable and editable, and machine-friendly.
|
||||
|
||||
For machine-friendliness, Nomad can also read JSON configurations. In general, we recommend
|
||||
using the HCL syntax.
|
||||
|
||||
Reference in New Issue
Block a user