[#10472] feat(entity store): support entity store read-replica connections#10471
Open
youngyjd wants to merge 4 commits intoapache:mainfrom
Open
[#10472] feat(entity store): support entity store read-replica connections#10471youngyjd wants to merge 4 commits intoapache:mainfrom
youngyjd wants to merge 4 commits intoapache:mainfrom
Conversation
Code Coverage Report
Files
|
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
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.
What changes were proposed in this pull request?
Why are the changes needed?
To allow offloading read-heavy metadata traffic to a read replica (e.g. MySQL) instead of the primary, improving scalability and reducing load on the primary while keeping writes and transactional reads on the primary.
Fix: #10472
Does this PR introduce any user-facing change?
Yes. New optional configuration options for the relational backend (jdbcReadOnlyUrl, jdbcReadOnlyUser, jdbcReadOnlyPassword, readOnlyMaxConnections, readOnlyMaxWaitMillis) and optional metrics for the read pool. Existing deployments are unchanged unless these options are set.
How was this patch tested?