API to stop task on the specially node or specially allocID

[xudawei]

Have one api for stop the task on specially node or specially alloc-id

In my sight，if i had run a job with service and count equal 3 ， some day i found one of the task worked not well . i hope to restart it or stop it , but i don't want to stop job , because it would be have down time . how can i kill the wrong task and restart it automaticlly .

how can i do ?

[jippi]

This is not possible today.

That kind of fine grained job control is planned, but AFAIK not in Q1 2017; hashicorp usually don't share their roadmap.

What I do today is kill the docker instance or task on the server directly using docker rm -f / docker stop or simply kill -9 the process (raw_exec & friends) - which will force nomad to restart the specific task.

Long term Nomad will be able to detect malfunctioning tasks using consul service health checks and will restart them on it's own initiative, but this is afaik also a bit out in the future :)

[dadgar]

@xudawei There currently is not this ability but we would like to bring it. I am going to rename and tag as enhancement

[xudawei]

@jippi @dadgar thank you for your replay . i got it

[dradtke]

This type of thing would be nice for enabling restarts for reasons other than task failure. For example, I'm working on an application that's deployed as a single binary, and when a new version is released, it would be nice to copy the new binary to the server and tell Nomad to restart it, rather than manually SIGHUP'ing it.

[jpialirci]

Is there status or a timeline for this enhancement? Thanks!

[tgross]

Implemented as nomad alloc stop and nomad alloc restart

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.