-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reboot Allocation #5670
Comments
👋 @Smithx10, Thanks for your issue, we're actually working to improve some of the control around this in 0.9.2. However, Nomad has a few pre-existing ways that will restart allocations:
And in Nomad 0.9.2, we'll be introducing support for manual restarts and signalling of tasks, as implemented in:
However, we don't currently support the delay_function from our rescheduling logic in local restarts. If that's a specific feature that you'd like to see added, I'd welcome another issue for it. Thanks again! |
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. |
Currently within the plugin architecture there is no way to reboot an instance in place. I'd like a way to reboot an allocation in place with an exponential back off. This would be similar to the container restartPolicy within Kubernetes Pod Lifecycle. https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy.
The idea is that by restarting the allocation, or sending a signal, someone could restore the allocation health at a cheaper cost than a full killing and restarting of a task. This would advantageous when paired with a service health check.
I'm new to Nomads ecosystem and perhaps have implemented Restart Incorrectly, but I don't think so.
The text was updated successfully, but these errors were encountered: