Skip to content
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.

Sign up for GitHub

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

core: fix node reservation scoring #7730

Merged
merged 5 commits into from
Apr 30, 2020
Merged

core: fix node reservation scoring #7730

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2781717
core: fix node reservation scoring
schmichael Apr 15, 2020
68aca51
docs: add #7730 to changelog
schmichael Apr 15, 2020
df4af4d
docs: mention scoring change from #7730
schmichael Apr 23, 2020
26d34f0
Update website/pages/docs/upgrade/upgrade-specific.mdx
schmichael Apr 30, 2020
e3cba0c
Merge branch 'master' into b-reserved-scoring
schmichael Apr 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 23 additions & 6 deletions website/pages/docs/upgrade/upgrade-specific.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,22 @@ details provided for their upgrades as a result of new features or changed
behavior. This page is used to document those details separately from the
standard upgrade flow.

## Nomad 0.11.2

### Scheduler Scoring Changes

Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
resources][reserved]
incorrectly during scoring. The result of this bug was that scoring biased in
favor of nodes with reserved resources vs nodes without reserved resources.

Placements will be more correct but slightly different in v0.11.2 vs earlier
versions of Nomad. Operators do *not* need to take any actions as the impact of
the bug and fix only minimally affect scoring.
schmichael marked this conversation as resolved.
Show resolved Hide resolved

Feasability (whether a node is capable of running a job at all) is *not*
affected.

## Nomad 0.11.0

### client.template: `vault_grace` deprecation
Expand Down Expand Up @@ -466,21 +482,22 @@ draining the node so no tasks are running on it. This can be verified by running
state. Once that is done the client can be killed, the `data_dir` should be
deleted and then Nomad 0.3.0 can be launched.

[dangling-containers]: /docs/drivers/docker#dangling-containers
[drain-api]: /api-docs/nodes#drain-node
[drain-cli]: /docs/commands/node/drain
[dangling-containers]: /docs/drivers/docker#dangling-containers
[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
[hcl2]: https://github.com/hashicorp/hcl2
[limits]: /docs/configuration#limits
[lxc]: /docs/drivers/external/lxc
[migrate]: /docs/job-specification/migrate
[plugins]: /docs/drivers/external
[plugin-stanza]: /docs/configuration/plugin
[preemption]: /docs/internals/scheduling/preemption
[plugins]: /docs/drivers/external
[preemption-api]: /api-docs/operator#update-scheduler-configuration
[preemption]: /docs/internals/scheduling/preemption
[reserved]: /docs/configuration/client#reserved-parameters
[task-config]: /docs/job-specification/task#config
[validate]: /docs/commands/job/validate
[vault_grace]: /docs/job-specification/template
[update]: /docs/job-specification/update
[tls-guide]: https://learn.hashicorp.com/nomad/transport-security/enable-tls
[tls-vault-guide]: https://learn.hashicorp.com/nomad/vault-integration/vault-pki-nomad
[update]: /docs/job-specification/update
[validate]: /docs/commands/job/validate
[vault_grace]: /docs/job-specification/template