Skip to content

Update coordinated-shutdown.md #32870

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.

Sign up for GitHub

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

Merged
patriknw merged 1 commit into from
Jan 5, 2026
+1 −1
Merged

Update coordinated-shutdown.md #32870

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion akka-docs/src/main/paradox/coordinated-shutdown.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ akka.coordinated-shutdown.run-by-jvm-shutdown-hook=off
Note that if running in Kubernetes, a SIGKILL will be issued after a set amount of time has passed
since SIGTERM. By default this time is 30 seconds ([`terminationGracePeriodSeconds`](https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#hook-handler-execution)):
it may be worth adjusting the Kubernetes configuration or the phase timeouts to make `CoordinatedShutdown`
more likely to completely exectue before SIGKILL is received.
more likely to completely execute before SIGKILL is received.

If you have application specific JVM shutdown hooks it's recommended that you register them via the
`CoordinatedShutdown` so that they are running before Akka internal shutdown hooks, e.g.
Expand Down