I ran an example of a Redis job, after that I created another similar job, but with a different name and I get these errors:
Placement Failures
cache 1 unplaced
- Constraint
missing network
filtered 1 node
- Resources exhausted on 1 node
- Dimension memory exhausted on 1 node
1 Like
Hi @marciosartini, are you able to share the two job files you are using as well as how you are running Nomad? This will help ensure we can resolve the problem you are seeing.
The latter errors that you detail indicate the Nomad client that is running the jobs has run out of memory available for allocation. In this situation, you would need to either lower the amount of memory resource allocated within each job, add another node into the cluster, or increase the size of the instance running.
Thanks,
jrasell and the Nomad team
1 Like
Hi, I have the same problem

job "project" {
datacenters = ["dc1"]
type = "service"
region = "global"
constraint {
attribute = "${attr.kernel.name}"
value = "linux"
}
group "postgres-project-group" {
network {
mode = "bridge"
port "postgres" {
to = 5432
host_network = "private"
}
}
service {
name = "project-data-store"
port = "postgres"
connect {
sidecar_service {}
}
}
task "postgres-project-task" {
driver = "docker"
config {
image = "postgres:13.4"
ports = "db"
}
env {
POSTGRES_PASSWORD = "project-password"
POSTGRES_DB = "project"
}
resources {
cpu = 2000
memory = 2000
}
}
}
group "ms-project-group" {
count = 1
network {
mode = "bridge"
port "project" {
to = 5000
host_network = "private"
}
}
service {
name = "ms-project"
connect {
sidecar_service {
proxy {
upstreams {
destination_name = "project-data-store"
local_bind_port = 5432
}
}
}
}
}
task "ms-project-task" {
driver = "docker"
config {
image = "docker/project"
port = "project"
}
resources {
cpu = 100
memory = 100
}
}
}
}