I’m pretty new to nomad and noticed the following:
- I stopped some jobs in the UI
- The jobs were marked as dead
- Some hours later I wanted to restart the jobs but they disappeared.
As far as I’ve unterstood from the documentation the job has been deleted by the next run of the garbage collection.
However temporarly stopping and restarting a job seems a pretty commun use-case to me.
(think of Linux-folks working with systemctl stop / systemctl restart). Is there something that I missed?
As far as I’ve unterstood from the documentation the job has been deleted by the next run of the garbage collection
Yes this is correct. Stopping a job currently is considered terminal from Nomad’s internal standpoint and therefore makes it eligible for garbage collection is a number of conditions are met.
stopping and restarting a job
Nomad does not currently have a notion of stopping/starting a job; when a service job is registered is it expected to run indefinitely. This issue tracks this enhancement and has additional conversation and context on the subject.
jrasell and the Nomad team