pd: add callee_id to RequestHeader #38
Merged
Conversation
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
`callee_id` is used to indicate the expected server ID to receive the request. The server **SHOULD** check if the `callee_id` matches its own ID, normally it's the client url address of the server. We encountered an issue where a tso client caches the stale DNS result and the new tso server takes over the old server's network address. Then, the tso client connects to the new tso server (a follower) with the actual leader's hostname, creating a hallucination that the leader is not the leader anymore. If the client meets this case, it might never get out of it if it doesn't refresh its DNS cache by reconnecting. ref tikv/pd#9894 Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
|
|
* Remove unnecessary file Signed-off-by: Neil Shen <overvenus@gmail.com> * Unify proto options * Do not generate XXX_ fields for Go protobuf structs * Enable lite runtime for Rust protobuf files Signed-off-by: Neil Shen <overvenus@gmail.com> * update go files Signed-off-by: Neil Shen <overvenus@gmail.com> * update proto lock file Signed-off-by: Neil Shen <overvenus@gmail.com> --------- Signed-off-by: Neil Shen <overvenus@gmail.com> Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
* Introduce QueryRegion stream Signed-off-by: JmPotato <ghzpotato@gmail.com> * Add prev_keys to QueryRegionRequest Signed-off-by: JmPotato <ghzpotato@gmail.com> --------- Signed-off-by: JmPotato <ghzpotato@gmail.com> Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
Signed-off-by: Ryan Leung <rleungx@gmail.com> Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
…llee-header Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
iosmanthus
force-pushed
the
iosmanthus/pd/8.5/callee-header
branch
from
e10109f to
d07b34e
Compare
…nto iosmanthus/pd/8.5/callee-header Signed-off-by: iosmanthus <myosmanthustree@gmail.com>
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.
callee_idis used to indicate the expected server ID to receive the request. The server SHOULD check if thecallee_idmatches its own ID, normally it's the client url address of the server. We encountered an issue where a tso client caches the stale DNS result and the new tso server takes over the old server's network address. Then, the tso client connects to the new tso server (a follower) with the actual leader's hostname, creating a hallucination that the leader is not the leader anymore. If the client meets this case, it might never get out of it if it doesn't refresh its DNS cache by reconnecting. ref tikv/pd#9894