Nomad does not correctly detect memory in Allocated Resources

[elvanowen]

I run nomad node status 9fb15cd7 on my nomad node and it returns 0/0 for the "Allocated Resources". This also happens to all other nodes in my cluster.

ID            = 9fb15cd7
Name          = nomad-test-sg-vm1
Class         = <none>
DC            = dc1
Drain         = false
Eligibility   = eligible
Status        = ready
Uptime        = 11760h48m31s
Driver Status = docker,exec,java

Node Events
Time                       Subsystem  Message
2018-12-21T18:18:59+08:00  Cluster    Node registered

Allocated Resources
CPU          Memory   Disk         IOPS
0/31200 MHz  0 B/0 B  0 B/1.7 GiB  0/0

Allocation Resource Utilization
CPU          Memory
0/31200 MHz  0 B/0 B

Host Resource Utilization
CPU            Memory         Disk
235/31200 MHz  11 GiB/31 GiB  207 GiB/885 GiB

Allocations
No allocations placed

OS: CentOS Linux release 7.5.1804 (Core)
Nomad Version: v0.8.6 (ab54ebc+CHANGES)

[elvanowen]

Below is my job definition

job "redis-exporter" {
  constraint {
    attribute = "${node.unique.name}"
    operator = "regexp"
    value = "nomad-test-sg-vm[1-2]"
  }

  region = "sg"

  datacenters = ["dc1"]

  group "redis-exporter" {
    task "redis-exporter" {
      driver = "docker"

      config {
        network_mode = "host"
        image = "oliver006/redis_exporter:v0.21.2"
        args = ["-redis.addr", "localhost:6379", "-web.listen-address", "localhost:9021"]
      }
    }
  }
}

And running nomad job plan redis-exporter.nomad return below error:

Scheduler dry-run:
- WARNING: Failed to place all allocations.
  Task Group "redis-exporter" (failed to place 1 allocation):
    * Constraint "${node.unique.name} regexp nomad-test-sg-vm[1-2]" filtered 1 nodes
    * Resources exhausted on 2 nodes
    * Dimension "memory" exhausted on 2 nodes

[burdandrei]

what is your resources stanza here?

[elvanowen]

We found out that we are using the wrong 32-bit binary instead of 64-bit binary. After updating to 64-bit binary, everything works fine.

[github-actions]

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.