In a project where there are multiple redis clusters being used, the redisLinks property will point to the nodes of the most recently created client. Given that a client can be created either by a user or by receiving a 'MOVED' command, there is almost no way of reliably determining what redisLinks is pointing to. Unless there is a really good reason for keeping redisLinks around, I am in favor of removing it from the API altogether.
Referring to the redisLinks property that is exposed through module.exports https://github.com/joaojeronimo/node_redis_cluster/blob/master/index.js#L317
In a project where there are multiple redis clusters being used, the redisLinks property will point to the nodes of the most recently created client. Given that a client can be created either by a user or by receiving a 'MOVED' command, there is almost no way of reliably determining what redisLinks is pointing to. Unless there is a really good reason for keeping redisLinks around, I am in favor of removing it from the API altogether.