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

if we make nomad restart "Allocation Resource Utilization" doen't show info on already allocated task #1365

Closed
tantra35 opened this issue Jun 28, 2016 · 1 comment

Comments

@tantra35
Copy link
Contributor

tantra35 commented Jun 28, 2016

Nomad version

Nomad v0.4.0-rc2

If on instance exist allocated tasks, and then we restart nomad(due for example change config, or upgrade binary process), and then we try to call nomad node-status ..., we see 0 in "Allocation Resource Utilization" sections:

root@social:/# nomad node-status -self
ID     = 57752a6b
Name   = social
Class  = <none>
DC     = test
Drain  = false
Status = initializing
Uptime = 369h11m44s

Allocated Resources
CPU       Memory           Disk            IOPS
900/2688  3.7 GiB/3.8 GiB  2.6 GiB/22 GiB  0/0

Allocation Resource Utilization
CPU     Memory
0/2688  0 B/3.8 GiB

Host Resource Utilization
CPU       Memory           Disk
630/3200  3.9 GiB/7.8 GiB  13 GiB/36 GiB

Allocations
ID        Eval ID   Job ID                       Task Group                   Desired Status  Client Status
cbe981fd  e5c73ae0  redis                        redis                        run             running
f1846f25  aa4879cf  redis                        redis                        stop            complete
3d0844d4  de665d7a  gardenscapesFBEntDynamoNode  gardenscapesFBEntDynamoNode  run             running
8387a5ff  4e223472  gardenscapesDynamo           gardenscapesDynamo           run             running
0e9a1038  d7c025b9  townshipMacDynamoNode        townshipMacDynamoNode        run             running
ad0481b7  3d0ad2d1  fishdomDDDynamoNode          fishdomDDDynamoNode          run             running

@github-actions
Copy link

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 21, 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