38 releases
new 0.15.2 | Nov 24, 2024 |
---|---|
0.15.1 | Jul 9, 2024 |
0.15.0 | Mar 30, 2024 |
0.14.2 | Dec 2, 2023 |
0.4.1 | Nov 28, 2021 |
#95 in Asynchronous
10,017 downloads per month
Used in 7 crates
(6 directly)
94KB
1.5K
SLoC
tokio-graceful-shutdown
This crate provides utility functions to perform a graceful shutdown on tokio-rs based services.
Specifically, it provides:
- Listening for shutdown requests from within subsystems
- Manual shutdown initiation from within subsystems
- Automatic shutdown on
- SIGINT/SIGTERM/Ctrl+C
- Subsystem failure
- Subsystem panic
- Clean shutdown procedure with timeout and error propagation
- Subsystem nesting
- Partial shutdown of a selected subsystem tree
Usage Example
async fn subsys1(subsys: SubsystemHandle) -> Result<()>
{
log::info!("Subsystem1 started.");
subsys.on_shutdown_requested().await;
log::info!("Subsystem1 stopped.");
Ok(())
}
This shows a very basic asynchronous subsystem that simply starts, waits for the program shutdown to be triggered, and then stops itself.
This subsystem can now be executed like this:
#[tokio::main]
async fn main() -> Result<()> {
Toplevel::new(|s| async move {
s.start(SubsystemBuilder::new("Subsys1", subsys1))
})
.catch_signals()
.handle_shutdown_requests(Duration::from_millis(1000))
.await
.map_err(Into::into)
}
The Toplevel
object is the root object of the subsystem tree.
Subsystems can then be started in it using the start()
method
of its SubsystemHandle
object.
The catch_signals()
method signals the Toplevel
object to listen for SIGINT/SIGTERM/Ctrl+C and initiate a shutdown thereafter.
handle_shutdown_requests()
is the final and most important method of Toplevel
. It idles until the program enters the shutdown mode. Then, it collects all the return values of the subsystems, determines the global error state and makes sure the shutdown completes within the given timeout.
Lastly, it returns an error value that can be directly used as a return code for main()
.
Further examples can be seen in the examples folder.
Building
To use this library in your project, enter your project directory and run:
cargo add tokio-graceful-shutdown
To run one of the examples (here 01_normal_shutdown.rs
), simply clone the tokio-graceful-shutdown repository, enter the repository folder and execute:
cargo run --example 01_normal_shutdown
Motivation
Performing a graceful shutdown on an asynchronous program is a non-trivial problem. There are several solutions, but they all have their drawbacks:
-
Global cancellation by forking with
tokio::select
. This is a wide-spread solution, but has the drawback that the cancelled tasks cannot react to it, so it's impossible for them to shut down gracefully. -
Forking with
tokio::spawn
and signalling the desire to shutdown running tasks with mechanisms liketokio::CancellationToken
. This allows tasks to shut down gracefully, but requires a lot of boilerplate code, like- Passing the tokens to the tasks
- Waiting for the tasks to finish
- Implementing a timeout mechanism to prevent hangs
- Collecting subsystem return values
- Making sure that subsystem errors get handled correctly
If then further functionality is required, as listening for signals like SIGINT or SIGTERM, the boilerplate code becomes quite messy.
And this is exactly what this crate aims to provide: clean abstractions to all this boilerplate code.
Contributions
Contributions are welcome!
I primarily wrote this crate for my own convenience, so any ideas for improvements are greatly appreciated.
Dependencies
~5–14MB
~147K SLoC