Fix sharded pub/sub handling over slot migrations by mgravell · Pull Request #2969 · StackExchange/StackExchange.Redis (original) (raw)
AFAIK there is no such thing as a dedicacted "discovery" connection, except perhaps in sentinel scenarios; I need to think on this - there's a timing thing here; in the migration process, the new node definitely knows, the old node knows (unless it is going offline), but the other nodes might not know yet (announcing this eagerly is explicitly documented as an optional step, otherwise it'll get the updates state "eventually"). But by definition we don't know which the new node is yet! So; unless we ask everyone, I think the old node is our best bet, and it is almost certainly still in the cluster at this point.