-
Notifications
You must be signed in to change notification settings - Fork 54
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
Implement graceful termination for the server, canceling outstanding operations #607
Labels
Comments
Added to epic #586 |
5 tasks
EronWright
changed the title
Implement graceful termination for the server, canceling outstanding operations.
Implement graceful termination for the server, canceling outstanding operations
Jul 24, 2024
Added to epic #586 |
Merged
blampe
added a commit
that referenced
this issue
Sep 24, 2024
This implements graceful shutdown by propagating interrupts to our child processes. Killing a workspace pod in the middle of an update will mark the Update as failed ("update canceled" error), and subsequent Updates will resume where it left off as you would expect. Fixes #607.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When the grpc server receives a shutdown signal (SIGINT), it should gracefully shutdown. It should not accept new RPC requests, and should wait for outstanding requests to complete.
Shutdown is usually due to a planned disruption, e.g. workspace pod termination due to a change to the project source or for node maintenance.
Ideally, any outstanding Pulumi deployment operation would be sent a CTRL-C signal to give it a chance to wind down gracefully. That's an unimplemented aspect of the core auto API: pulumi/pulumi#13160
The text was updated successfully, but these errors were encountered: