[CASSSIDECAR-495] Report each instance's own Sidecar instance id in th… - #380
Open
bianca-stanciu29 wants to merge 1 commit into
Open
[CASSSIDECAR-495] Report each instance's own Sidecar instance id in th…#380bianca-stanciu29 wants to merge 1 commit into
bianca-stanciu29 wants to merge 1 commit into
Conversation
…e ring / token-range-replicas response Enrich RingEntry and ReplicaMetadata with the id of the local Sidecar instance managing each node/replica, resolved via InstanceMetadataFetcher#sidecarInstanceId(host) in KeyspaceRingHandler and TokenRangeReplicaMapHandler. Entries not managed by this Sidecar retain a null id. This lets clients discover which instanceId to pass for a given node/replica in a follow-up request, which matters most when the client sits behind a load balancer and cannot otherwise guarantee it reaches the Sidecar managing that node.
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
1 participant
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.
…e ring / token-range-replicas response
Enrich RingEntry and ReplicaMetadata with the id of the local Sidecar instance managing each node/replica, resolved via
InstanceMetadataFetcher#sidecarInstanceId(host) in KeyspaceRingHandler and TokenRangeReplicaMapHandler. Entries not managed by this Sidecar retain a null id. This lets clients discover which instanceId to pass for a given node/replica in a follow-up request, which matters most when the client sits behind a load balancer and cannot otherwise guarantee it reaches the Sidecar managing that node.