-
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
nomad.nomad.blocked_evals.job.cpu unexpected values #12848
Comments
I also see negative values.
|
This was referenced May 24, 2022
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Nomad version
Operating system and Environment details
Issue
The metric
nomad.nomad.blocked_evals.job.cpu
emits incorrect values while submitting jobs with cpu resources defined.Reproduction steps
nomad.nomad.blocked_evals.job.cpu
and initially it looks correct.nomad.nomad.blocked_evals.job.cpu
after deployment and the metric value seems incorrect.There are no blocked evals because there are available resources. Now I'm going to deploy a new job that purposefully has cpu resources elevated beyond the cluster capacity.
*^ this value is correct. I see 4000
json.Gauges[1].Value = 4000;
Now if I modify the same jobspec and change the cpu resource value from 4000 to 3500 I'd expect the value
json.Gauges[1].Value = 3500;
. However, the value will stick at 4000Expected Result
I expect the metric value to reflect the needed value of the pending job task.
Actual Result
The pending job requires 4000 cpu but the cluster does not have the capacity, and needs 4000 cpu in order to run the job. I modify the same jobspec to a value of 3500 cpu, which is still above available capacity. The expectation is that the results of curling the metric value
nomad.nomad.blocked_evals.job.cpu
would output a metric of 3500 cpu, but the value is still 4000.Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: