Skip to content
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.

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

[4.4] Fix pool closing connections too aggressively #1038

Merged
merged 6 commits into from
Apr 12, 2024

Conversation

robsdedude
Copy link
Member

Whenever a new routing table was fetched, the pool would close all connections to servers that were not part of the routing table. However, it might well be, that a missing server is present still in the routing table for another database. Hence, the pool now checks the routing tables for all databases before deciding which connections are no longer needed.g

Backport of #955

Whenever a new routing table was fetched, the pool would close all connections
to servers that were not part of the routing table. However, it might well be,
that a missing server is present still in the routing table for another
database. Hence, the pool now checks the routing tables for all databases before
deciding which connections are no longer needed.g
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐕‍🦺

(Wasn't it possible to backport the tests?)

@robsdedude robsdedude enabled auto-merge (squash) April 12, 2024 13:23
@robsdedude robsdedude merged commit 249c10b into neo4j:4.4 Apr 12, 2024
12 checks passed
@robsdedude robsdedude deleted the fix/too-aggressive-pool-cleaning-4.4 branch April 12, 2024 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants