fix: Destroy network communication channels used in replication on shutdown#4005
Merged
fix: Destroy network communication channels used in replication on shutdown#4005
Conversation
colinbarry
approved these changes
Apr 9, 2026
Contributor
colinbarry
left a comment
There was a problem hiding this comment.
Approved, with note about perhaps documenting the constness of these functions.
|
Contributor
Author
Tracking
Standard development
CI Testing Labels
Documentation checklist
|
61 tasks
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
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.



Abort socket before closing thread pool and destroying client in order to unblock the shutdown. Also, take read lock on shutdown to allow concurrent shutdown with replication.