Skip to content

Refresh routing table using a separated thread #216

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

Merged
merged 4 commits into from
Feb 12, 2025

Conversation

madchicken
Copy link
Collaborator

As promised, here is a follow-up PR to fetch and update the routing table using a separated thread.
This pull request introduces significant changes to the routing and connection management within the lib/src directory, specifically focusing on the graph.rs, connection_registry.rs, and routed_connection_manager.rs files. The changes include adding a new RoutingTableProvider trait, implementing a ClusterRoutingTableProvider, and refactoring the connection registry and routed connection manager to support these updates.

Improvements to Routing and Connection Management:

@madchicken madchicken force-pushed the use-thread-for-rt-update branch from 7306165 to 1e8a534 Compare January 17, 2025 12:19
Copy link
Collaborator

@knutwalker knutwalker left a comment

Choose a reason for hiding this comment

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

Thanks, greatly appreciate it! Happy to merge once my comment is resolved.

@madchicken madchicken force-pushed the use-thread-for-rt-update branch from 4353bcb to c451351 Compare January 28, 2025 11:22
@madchicken madchicken requested a review from knutwalker February 6, 2025 13:48
@knutwalker knutwalker merged commit 062ba43 into neo4j-labs:main Feb 12, 2025
11 checks passed
@madchicken madchicken deleted the use-thread-for-rt-update branch February 22, 2025 13:10
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