LaxConnPool: Loop over expired connections #610
Merged
Conversation
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
This change brings `LaxConnPool` into alignment with `StrictConnPool`, which loops over pool entries and discards expired ones as they are discovered, instead of returning them.
ok2c
approved these changes
Jan 29, 2026
Member
|
@rschmitt Could you please cherry-pick it to 5.4.x? |
Contributor
Author
|
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change brings
LaxConnPoolinto alignment withStrictConnPoolandRouteSegmentedConnPool, which loop over pool entries and discard expired ones as they are discovered, instead of returning them.