Task CPU usage reads 0% after extended period
Open
stage/needs-discussion
theme/driver/exec
theme/metrics
type/bug
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
I'm trying to track a strange behavior on my nomad cluster.
After several days, tasks begin to read always 0 mhz cpu usage. If I deploy the job again, the reads will be back to normal, until they go to zero again.
I have a cluster deployed purely on Ubuntu 20.04, using Nomad 1.04.
I would appreciate any help on steps to identify what's messing with the cpu reads in my setup.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.