Support load balancing of connection on multiple clusters #26
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.
Problem statement:
In a multi-cluster environment, the current implementation of the pgjdbc driver fails to handle connections correctly. The clusterinfomap does not distinguish between nodes belonging to different clusters. As a result:
This lack of demarcation for nodes across clusters prevents reliable support for multi-cluster deployments and introduces ambiguity in connection routing.
Changes made:
A new column, universe_uuid, is to be introduced in the existing yb_servers function. This column will serve as a unique identifier for the universe (cluster) to which each server belongs.
Details of the implementation provided in this doc.
Testing
Test cases being added to the driver-examples repo. TODO: Add link here once done