hunts / clustedis Goto Github PK

Supports two cases:

1. All reads go to slaves
2. Only when master failed, send reads to slaves

Both of these two cases can be set on client redisOptions.

Init the cluster client have to provide one or more entry node(s) address. But some nodes may became death by reason of master-slave failover happened or other changes made to configuration.

The factory method have to be able to init a client as long as there's one live node in the given node list.

Because of both Redis and Node.js are single-thread mode. Use pooling do not take any benefit but waste resource of node.

In some cases, when need to know all keys of a command received from client.

The function will be like:

var map = client.knownKeys(args);

The key of the map is the position (index) in the arguments array.
The value of the map is the redis key.

For example:

var args = ['key1', 'value1', 'key2', 'value2'];

This may be the args of mset. The result of .knowKeys(args) will be:

{0: 'key1', 2: 'key2'}

Deal with .travis.yml

A master may become unavailable, and one of its slave can take its place.

For this case, when master is unavailable, queue the commands. Wait until new master is selected, refresh the connection pool and replay queued commands.