feat(java): add cluster metadata and leader redirection to TCP client#3745
Open
mmodzelewski wants to merge 1 commit into
Open
feat(java): add cluster metadata and leader redirection to TCP client#3745mmodzelewski wants to merge 1 commit into
mmodzelewski wants to merge 1 commit into
Conversation
Java clients connected to a VSR follower had no way to discover the cluster leader, so operations against a multi-node cluster failed until the user manually pointed the client at the right node. Add the GET_CLUSTER_METADATA command with cluster roster models and a binary deserializer. After login the async TCP client fetches the roster and, when a healthy leader with an enabled TCP endpoint lives elsewhere, reconnects to it and replays the login. Redirections are capped at 3 consecutive hops so two nodes both claiming leadership cannot ping-pong a client, and every failure on the redirect path is non-fatal: the client stays on the current node. Mirrors the Rust and Go SDKs. Covered by a leader_redirection BDD scenario wired into the cluster docker-compose setup.
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
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.
Java clients connected to a VSR follower had no way to discover
the cluster leader, so operations against a multi-node cluster
failed until the user manually pointed the client at the right
node.
Add the GET_CLUSTER_METADATA command with cluster roster models
and a binary deserializer. After login the async TCP client
fetches the roster and, when a healthy leader with an enabled
TCP endpoint lives elsewhere, reconnects to it and replays the
login. Redirections are capped at 3 consecutive hops so two
nodes both claiming leadership cannot ping-pong a client, and
every failure on the redirect path is non-fatal: the client
stays on the current node. Mirrors the Rust and Go SDKs.
Covered by a leader_redirection BDD scenario wired into the
cluster docker-compose setup.