You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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.
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: