*: fix the max recv message size for the client#1952
Merged
sre-bot merged 1 commit intotikv:release-3.0from Nov 19, 2019
Merged
*: fix the max recv message size for the client#1952sre-bot merged 1 commit intotikv:release-3.0from
sre-bot merged 1 commit intotikv:release-3.0from
Conversation
Signed-off-by: Ryan Leung <rleungx@gmail.com>
Member
Author
|
/run-all-tests |
nolouch
approved these changes
Nov 19, 2019
lhy1024
approved these changes
Nov 19, 2019
Contributor
|
/merge |
sre-bot
added
the
status/can-merge
Contributor
|
/run-all-tests |
rleungx
added a commit
to rleungx/pd
that referenced
this pull request
Nov 25, 2019
Signed-off-by: Ryan Leung <rleungx@gmail.com>
nolouch
pushed a commit
that referenced
this pull request
Nov 25, 2019
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.
What problem does this PR solve?
PR #1739 accidentally removes the max gRPC receive message size constraint for the client.
What is changed and how it works?
This PR fixes it by adding it back.
Check List
Tests
Related changes