peerswapd: make shutdown signal delivery reliable - #456
Open
daixiheguu wants to merge 1 commit into
Open
Conversation
Signed-off-by: daixiheguu <daixihegu@outlook.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use a one-element buffered channel for process signals and unregister it with
signal.Stopduring shutdown.os/signal.Notifydoes not block when delivering a signal, so an unbuffered channel can lose a signal when the receiver is not ready. The channel also should not be closed while it remains registered withos/signal, because a later delivery could panic.This keeps the existing shutdown flow while making signal ownership and delivery safe.
Tested with:
go test ./cmd/peerswaplnd/peerswapd