-
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
Placement failed due to CPU resource exhaustion, 2 servers going unused. #4347
Comments
I did just think of one possible thing that may be involved in this. On the 2 nodes that are currently not being alloc'd on, I did perform a Current output of
nodes
|
Can you try running: |
Ahh interesting. Must have missed the release note about that flag! Enabling eligibility on those 2 nodes fixed the issue. Thanks! |
Some sort of feedback in the Web UI about eligibility would be really nice. There's nothing in there at all as of 0.8.3. |
@glimberg Indeed, thanks for the feedback! We'll add it to our internal backlog. |
Also there may be a bug in disabling drain. According to the docs page for the eligibility command, disabling drain should restore eligibility. It didn't in this case. |
@glimberg for the suspected disable drain bug, would you mind opening a separate issue for that? Thank you! |
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. |
Nomad version
Nomad v0.8.3 (c85483d)
Operating system and Environment details
CentOS 7
Issue
I updated a job this morning to add 2 more groups into the job specification for 2 new instances of the service I'm managing via Nomad. After updating the job specification I received the following error:
I have 7 servers acting as nomad clients in this cluster. Not 5. 2 of the nomad clients have 0 allocs on them and have plenty of CPU to spare and nomad lists them as 'ready', but it won't alloc any jobs on there.
No errors in the logs and I'm not sure how to reproduce this issue. Job file is attached.
Job file:
The text was updated successfully, but these errors were encountered: