-
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: remove cores/memory beta label, update driver cpu docs #16175
Conversation
e151b4d
to
40ffb8c
Compare
@@ -1138,6 +1138,11 @@ many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`. | |||
Please keep the implications of CPU shares in mind when you load test workloads | |||
on Nomad. | |||
|
|||
If resources [cores][cores] is set, the task is given an isolated reserved set of |
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.
If resources [cores][cores] is set, the task is given an isolated reserved set of | |
If resources [`cores`][cores] is set, the task is given an isolated reserved set of |
If resources [cores][cores] is set, the task is given an isolated reserved set of | ||
CPU cores to make use of. The total set of cores the task may run on is the private | ||
set combined with the variable set of unreserved cores. The private set of CPU cores | ||
is available to your process by reading `NOMAD_CPU_CORES`. |
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.
Maybe link NOMAD_CPU_CORES
to https://developer.hashicorp.com/nomad/docs/runtime/environment#job-related-variables?
for the task. This may not be used with `cpu`. | ||
- `cores` <code>(`int`: <optional>)</code> - Specifies the number of CPU cores | ||
to reserve specifically for the task. This may not be used with `cpu`. The behavior | ||
of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]). |
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.
I wonder if it would make sense to expand task driver capabilities to include core reservation. That way we would be able to validate if the a task uses cores
with a task driver that doesn't support it.
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.
Interesting idea - added to https://github.com/hashicorp/team-nomad/issues/373 along with thinking of PSI uses
Closes #13775