Cluster node is automatically disconnected when it has no slots

I tried this code and I only see any logs in the then or catch

logger.debug('%s MEET Sending: %s', id, cmd);
// Tried also redis.cluster('meet', ip, port).then ...
redis.cluster(['meet', ip, port]).then((response) => {
        logger.info('%s MEET %s', id, response);
        return response;
    }).catch((err) => {
        logger.error(err, '%s Cannot MEET', id);
        return {error: true};
    });

It would be nice to have some examples too.

[luin]

It looks like that ioredis does not stay connected because there are no slots.

Yes, the behavior is expected. When there’s no slots (or no cluster nodes), ioredis will reconnect to cluster in order to connect to the new nodes once the cluster has been set up.

You are supposed to pass an array of IPs to new IoRedis.Cluster(…). Is it supposed to automatically pick up a new node when it joins or how do you add the new node?

ioredis is able to discover new node automatically, so you can just provide some of the nodes in the cluster instead of providing all of them.

Any reason why if there are no slots, ioredis automatically disconnect?

The root reason of that is because ioredis doesn’t know where the commands should be sent to when CLUSTER SLOTS returns [] since it relies on CLUSTER SLOTS command to know which nodes are in the cluster.

What if I want to write a script in node to setup the cluster?

That’s a good question. This issue happens basically because Cluster class is designed to work with a cluster that already set. You can use Redis class to send the MEET or any commands to setup the cluster (and since you already know the IPs of the target node, so this way should be pretty straightforward).

[ccinelli]

The problem seems to be here: https://github.com/luin/ioredis/blob/master/lib/cluster/ConnectionPool.ts#L126 Any reason why if there are no slots, ioredis automatically disconnect? Can this behavior at least be optional ?