Read from slaves with replication

Hi,

I’m planning to use ioredis with redis-connect for a distributed express application with consistent sessions.

My doubt, after reading the docs, I’ve assumed the following:

• Clustering is not needed for session storage, the data won’t be enough big.
• The majority of the operations will be reads in order to transform cookies into a req.session.

having the following nodes:

• Node A master (with a known ip).
• Node B slave (replica) of A (localhost).
• Node C slave (replica) of A (other node, unknown ip).

I can not perform write operations to B, even if I set slave-read-only to no, the updates won’t propagate, I need to write to A, so…

var Redis = require('ioredis');
var redis = new Redis('a-ip', port);

redis.set('foo', 'bar');
redis.get('foo', function (err, result) {
  console.log(result);
});

The ideal behavior would be, I am node B, I open a session, so I go A and set it, then the client comes in again, and I have to identify the cookie, so I read from B (localhost). Is this possible?

[luin]

@toredash It depends on what you think is read-write splitting. The discussions above consider “read-write splitting” as an automatic way to send different commands to different nodes via ONE Redis instance. Your example works, while developers have to do the splitting themselves.

[luin]

@dev-drprasad That’s supported in the cluster mode. Otherwise, you may refer to @toredash 's approach.