-
Notifications
You must be signed in to change notification settings - Fork 118
Support grpc forward (#198) #208
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
Support grpc forward (#198) #208
Conversation
|
/run-all-tests |
birdstorm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/merge |
|
/run-all-tests |
|
@ti-srebot merge failed. |
a2f5d62 to
239838a
Compare
* support grpc forward for tikv client Signed-off-by: Little-Wallace <bupt2013211450@gmail.com> Signed-off-by: birdstorm <samuelwyf@hotmail.com>
239838a to
374ae9e
Compare
birdstorm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/merge |
|
/run-all-tests |
|
@ti-srebot merge failed. |
Signed-off-by: birdstorm <samuelwyf@hotmail.com>
|
/merge |
|
/run-all-tests |
birdstorm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
cherry-pick #198 to release-3.1
You can switch your code base to this Pull Request by using git-extras:
# In client-java repo: git pr https://github.com/tikv/client-java/pull/208After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
When TiKV cluster deploy in three IDC A/B/C, if there is network isolation between the A and B, the message which should be send to leader in A can be forward by B.
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes