-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs and Changelog catch up #7010
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -98,6 +98,13 @@ server { | |
deployment must be in the terminal state before it is eligible for garbage | ||
collection. This is specified using a label suffix like "30s" or "1h". | ||
|
||
- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]: | ||
nil)</code> - Specifies the initial default scheduler config when | ||
bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or | ||
value is updated through the [API endpoint][update-scheduler-config]. See [the | ||
example section](#configuring-scheduler-config) for more details | ||
`default_scheduler_config` was introduced in Nomad 0.11.4. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nomad 0.10.4 |
||
|
||
- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a | ||
grace period beyond the heartbeat TTL of nodes to account for network and | ||
processing delays as well as clock skew. This is specified using a label | ||
|
@@ -232,5 +239,31 @@ server { | |
} | ||
``` | ||
|
||
### Configuring Scheduler Config | ||
|
||
This example shows enabling preemption for all schedulers. | ||
|
||
```hcl | ||
server { | ||
default_scheduler_config { | ||
preemption_config { | ||
batch_scheduler_enabled = true | ||
system_scheduler_enabled = true | ||
service_scheduler_enabled = true | ||
} | ||
} | ||
} | ||
``` | ||
|
||
The structure matches the [Update Scheduler Config][update-scheduler-config] endpoint, | ||
but adopted to hcl syntax (namely using snake case rather than camel case). | ||
|
||
Nomad servers check their `default_scheduler_config` only during cluster | ||
bootstrap. During upgrades, if a previously bootstrapped cluster already set | ||
scheduler configuration via the [Update Scheduler Config][update-scheduler-config] | ||
endpoint, that is always preferred. | ||
|
||
|
||
[encryption]: /guides/security/encryption.html "Nomad Encryption Overview" | ||
[server-join]: /docs/configuration/server_join.html "Server Join" | ||
[update-scheduler-config]: /api/operator.html#update-scheduler-configuration "Scheduler Config" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when bootstrapping a cluster