Cherry pick follower read to TiDB (#11347)#13464
Merged
Merged
Conversation
Member
Author
Member
Author
|
The original cherry-pick PR to 3.1 is #12535 |
coocood
force-pushed
the
release-3.1.6
branch
from
0ed2620 to
26ecea4
Compare
Member
Author
|
/run-all-tests |
cherry pick pingcap#11347 to 3.1 Fix code conflicts from 4.0 to 3.1. Users can use tidb_replica_read session variable to choose reading from leader or follower. To make it consistent with existing behavior, leader will be used by default unless follower is explicitly specified otherwise. Add a session scope variable tidb_replica_read to specify if TiDB should read data from leader or follower.
coocood
force-pushed
the
release-3.1.6
branch
from
26ecea4 to
7695dc8
Compare
Member
Author
|
/run-all-tests |
Member
Author
|
/run-all-tests tikv=release-3.1 |
Member
Author
|
/run-all-tests tikv=release-3.1 pd=release-3.1 |
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
4 participants
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.
cherry pick #11347 to 3.1
Fix code conflicts from 4.0 to 3.1. Users can use tidb_replica_read session variable to choose reading from leader or follower. To make it consistent with existing behavior, leader will be used by default unless follower is explicitly specified otherwise.
Add a session scope variable tidb_replica_read to specify if TiDB should read data from leader or follower.