whatyouhide / redix / e771af793b84c15bb3f95f5011a274932fa87a9b-PR-331

90%

main: 90%

Pull #331

github

Connect on demand for ASK redirects in cluster

The classic ASK scenario is a slot migrating to a brand-new node: a node
serving zero slots doesn't appear in CLUSTER SLOTS at all, so it has no
Registry entry and no topology refresh will ever connect it. Until now
handle_ask_redirect/6 returned a fabricated "ASK to unreachable node"
error on a Registry miss, so every ASK-redirected command failed until
the first slot migration completed, breaking scale-out resharding.

Mirror the MOVED fallback: on a Registry miss, connect on demand via
Manager.connect_to_node/2. ASK targets are cluster members, and the next
ensure_connections adopts or terminates the connection just like for
MOVED, so a bogus address can't leak connections.

Fixes #319.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

5 of 5 new or added lines in 1 file covered. (100.0%)

1163 of 1297 relevant lines covered (89.67%)

3648.56 hits per line