Keep seed router address in the pool after routing table #931
Conversation
This file contains 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
Forgetting the seed router was causing the connection to the seed router being recreated whenever the routing table is fetched and the seed router is not part of the cluster formation. For cases where the database name is set in the session, the driver will have to fetch the routing table for the default/home database for discovering the database name and make it consitent during the session lifetime. In this scenario, the seed router will be always used during the discovery. So, a new connection to the seed router will be created for each session. The solution for this issue is to keep the seed router in the pool during the update routing table process. This way, the same connections for the seed router can be re-used.
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.
Forgetting the seed router was causing the connection to the seed router being recreated whenever the routing table is fetched and the seed router is not part of the cluster formation. For cases where the database name is set in the session, the driver will have to fetch the routing table for the default/home database for discovering the database name and make it consitent during the session lifetime. In this scenario, the seed router will be always used during the discovery. So, a new connection to the seed router will be created for each session.
The solution for this issue is to keep the seed router in the pool during the update routing table process. This way, the same connections for the seed router can be re-used.