I recently ran into an issue where Nomad has reserved too much CPU & memory althoough configured otherwise. This can result in tasks being killed by the OOMKill.
OOM Killed
Workaround
There is a workaround by overriding the available memory and/or CPU power in your Nomad client config file.
Nomad client config
You can compute your "real" CPU compute power by multiplying the number of cores with the MHz. Example: 4 core CPU with 2 GHz each = 4 * 2000 = 8000.
To get your CPUs clock speed, use the lscpu util:
lscpu | grep MHz
The Nomad client config is located at /etc/nomad/nomad.hcl by default.
client {
memory_total_mb = 16000
cpu_total_compute = 8000
}
Sources
Allow for 0 res allocations / Disable resource constraints for particular agent #5672
Hashicorp Nomad and the memory options with the docker driver
Read more...
Get TTS with natural Voices on macOS without external Tools
You don't need fancy tool to get Text-to-Speech on macOS, even baked into Firefox
Stop all Adobe & Creative Cloud Processes on macOS via Script
Installing any Adobe Software on your computer comes with a huge load of bloatware. Stop all of this with a simple shell script.
Comments