You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using nomad version 0.9.4 32 bit on windows 2016 and the memory resources of the client gets reported as 0. Setting the "memory_total_mb" in the client config did not make a difference. The same issue was reported here: #5048
Here's the output of the 32 bit nomad
nomad node status 2a2a3d91
ID = 2a2a3d91
Name = Ops1
Class = <none>
DC = aws
Drain = false
Eligibility = eligible
Status = ready
Uptime = 70h12m28s
Driver Status = raw_exec
Node Events
Time Subsystem Message
2019-08-15T13:18:37Z Cluster Node registered
Allocated Resources
CPU Memory Disk
0/5000 MHz 0 B/0 B 0 B/76 GiB
Allocation Resource Utilization
CPU Memory
0/5000 MHz 0 B/0 B
Host Resource Utilization
CPU Memory Disk
138/5000 MHz 1.4 GiB/3.9 GiB (c:)
Allocations
No allocations placed
Here's the 64 bit running on the same server
nomad node status 2a2a3d91
ID = 2a2a3d91
Name = Ops1
Class = <none>
DC = aws
Drain = false
Eligibility = eligible
Status = ready
Uptime = 70h26m59s
Driver Status = raw_exec
Node Events
Time Subsystem Message
2019-08-15T13:54:23Z Cluster Node re-registered
2019-08-15T13:53:25Z Cluster Node heartbeat missed
2019-08-15T13:18:37Z Cluster Node registered
Allocated Resources
CPU Memory Disk
200/5000 MHz 600 MiB/3.0 GiB 600 MiB/76 GiB
Allocation Resource Utilization
CPU Memory
0/5000 MHz 59 MiB/3.0 GiB
Host Resource Utilization
CPU Memory Disk
3611/5000 MHz 1.6 GiB/3.9 GiB (c:)
The text was updated successfully, but these errors were encountered:
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.
Using nomad version 0.9.4 32 bit on windows 2016 and the memory resources of the client gets reported as 0. Setting the "memory_total_mb" in the client config did not make a difference. The same issue was reported here: #5048
Here's the output of the 32 bit nomad
Here's the 64 bit running on the same server
The text was updated successfully, but these errors were encountered: