Conversation
…d by the cluster. Previously it was set to what the user inputted, which led to errors with localhost not being redirected. Signed-off-by: Argus Li <[email protected]>
ravjotbrar
approved these changes
Mar 27, 2026
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.
Description
The cluster nodes advertise their internal IPs (192.168.12.x:700x), but the user connects via localhost:7001. After the GlideClusterClient performs its initial topology refresh, it replaces the seed address with the cluster-advertised addresses. This routes INFO to localhost:7001, but the GlideClusterClient no longer has that address in its topology — it only knows 192.168.12.43:7001. So it throws ConnectionNotFoundForRoute.
This change uses the actual address advertised by the cluster for the node.