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.

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

Wrong resource allocation stats and host resource after upgrade to nomad #1374

Closed
tantra35 opened this issue Jun 30, 2016 · 2 comments
Closed

Comments

@tantra35
Copy link
Contributor

tantra35 commented Jun 30, 2016

Nomad version

Nomad v0.4.0

Operating system and Environment details

Linux consulnomad01 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Issue

On some of our nodes in production we see 0 in resource utilization,after upgrade to nomad 0.4, but this data is wrong, because this is not possible

root@consulnomad01:/home/ruslan# nomad node-status 497928a2
ID     = 497928a2
Name   = ip-172-30-0-39
Class  = fishdom
DC     = aws
Drain  = false
Status = ready
Uptime = 852h42m51s

Allocated Resources
CPU        Memory           Disk            IOPS
1200/5800  3.6 GiB/3.7 GiB  2.3 GiB/27 GiB  0/0

Allocation Resource Utilization
CPU       Memory
927/5800  0 B/3.7 GiB

Host Resource Utilization
CPU        Memory           Disk
1454/5800  1.3 GiB/3.7 GiB  0 B/0 B

Allocations
ID        Eval ID   Job ID                    Task Group                Desired Status  Client Status
6b9b38b1  06ce6809  gardenscapesFBDynamoNode  gardenscapesFBDynamoNode  run             running
ca00c1bf  49f75b05  gardenscapesDynamo        gardenscapesDynamo        run             running
95c07e6b  da99f963  fishdomDDDynamoNode       fishdomDDDynamoNode       run             running
1b0d75dd  205be050  townshipMacDynamoNode     townshipMacDynamoNode     run             running

In this output Host resource utilization must be about 2GB/32GB, and memory utilization in Allocation Resource Utilization also can't be 0

@dadgar
Copy link
Contributor

dadgar commented Sep 21, 2017

This hasn't been an issue in any of the recent releases. We can re-open if you are still seeing this.

@dadgar dadgar closed this as completed Sep 21, 2017
@github-actions
Copy link

github-actions bot commented Dec 7, 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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants