Nomad: task health check to kill & replace
It would be great to be able to register a task health check in a job definition (a la Consul) that, optionally, could be leveraged by Nomad to kill and replace a failed task.
ProbablyRusty
All 9 comments
This will be included in our consul integration (probably in 0.2).
cbednarski
on 15 Oct 2015
This would be really nice to have. Are there any updates @cbednarski?
c4milo
on 1 Feb 2016
@cbednarski is this already implemented?
abhidrona
on 22 Jun 2016
@abhidrona No it is not! Nomad will register services and checks but does not use the state of the checks to restart tasks.
dadgar
on 22 Jun 2016
I'm not sure what the priority is for this, but IMHO it should be of highest priority.
Using service health checks but no task health checks, Nomad creates a zombie fleet of tasks.
What exactly is the point of having unhealthy jobs non-discoverable but still running?
stongo
on 13 Oct 2016
This also is one of the very few issues that keep us from switching over from mesos to nomad. (We run nomad in our staging environment, but can't afford to manually restart tasks in production.)
memelet
on 23 May 2017
Closing in favor of https://github.com/hashicorp/nomad/issues/876 given more people have seen that one.
dadgar
on 23 Jun 2017
@dadgar this is #164
c4milo
on 23 Jun 2017
Fixed reference! My bad!
dadgar
on 23 Jun 2017
Related issues
stongo
路
3Comments
jippi
路
3Comments
DanielDent
路
3Comments
bdclark
路
3Comments
byronwolfman
路
3Comments
Most helpful comment
I'm not sure what the priority is for this, but IMHO it should be of highest priority.
Using service health checks but no task health checks, Nomad creates a zombie fleet of tasks.
What exactly is the point of having unhealthy jobs non-discoverable but still running?