Describe the bug
GlideClusterClient.SelectAsync explicitly routes to Route.Random, but glide-core's default routing for SELECT is AllNodes. When switching databases in a cluster, all nodes should update their selected database — not just a random one.
Expected Behavior
SELECT should be sent to all nodes (AllNodes) so the database selection is consistent across the cluster.
Current Behavior
Only a single random node receives the SELECT command, leaving other nodes on the previous database.
Possible Solution
Remove the explicit Route.Random parameter from GlideClusterClient.SelectAsync so glide-core's correct AllNodes default applies.
Related
Describe the bug
GlideClusterClient.SelectAsyncexplicitly routes toRoute.Random, but glide-core's default routing forSELECTisAllNodes. When switching databases in a cluster, all nodes should update their selected database — not just a random one.Expected Behavior
SELECTshould be sent to all nodes (AllNodes) so the database selection is consistent across the cluster.Current Behavior
Only a single random node receives the
SELECTcommand, leaving other nodes on the previous database.Possible Solution
Remove the explicit
Route.Randomparameter fromGlideClusterClient.SelectAsyncso glide-core's correctAllNodesdefault applies.Related