-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Agent always detect node IOPS to 0 #2825
Comments
It's a documentation issue.. IOPS can be configured inside the Simply add Afaik nomad does no effort to detect the iops for a device, as there are no reliable way to do so. AWS could potentially be detected iops for based on the EBS volume, but probably not worth the effort |
Isn't the location you linked in the source code a configuration option about reserved resources ? https://www.nomadproject.io/docs/agent/configuration/client.html#reserved
|
You are right @mildred - sorry :) |
Right now specifying IOPS in a job only affects That cgroup only accepts a weight from 10-1000, so there's nothing to detect or set for the client. It should become a more portable IOP provisioning system in the future, but it's use is limited today. Sorry for the confusion! Our docs definitely don't explain it correctly! |
Oops, but I neglected to notice that the scheduler treats IOPS as an absolute resource. So your bug is valid, and there's more to it than I originally suspected! Reopening. |
It's been more than a year and the docs are still lying about this, is there anywhere to submit PRs to fix mistruthful docs? |
Yes! You can submit a PR against our entire website as its located in the The readme covers building/testing locally. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
When starting a nomad agent on a node, it detects the available IOPS on that node to 0. it doesn't seem there is a way to override that.
Either you should allow the nomad agent to override the detected IOPS available (you kave a
-network-speed
option to override the network speed) and document it, or you should remove the IOPS information from the documentation.The text was updated successfully, but these errors were encountered: