Support scaleReads

[idahogurl]

Support plan

• is this issue currently blocking your project? Yes
• is this issue affecting a production system? Yes

Context

• node version: 10.x
• module version: 5.0.2
• environment (e.g. node, browser, native): Node
• used with (e.g. hapi application, another framework, standalone, ...): hapi application
• any other relevant information:

What problem are you trying to solve?

Our web site is having show-stopping performance issues and we are trying to setup a second Redis instance that is a read-only.

catbox-redis supports clusters but it does not support the Redis option of scaleReads. I found you closed #61 as you determined using a custom Redis client was sufficient. According to the documentation, a custom client must:

• be manually started and stopped,
• be compatible with the ioredis module API, and
• expose the status property that must be set to 'ready' when connected

I was able to get the start to work but @hapijs/hapi handles all the situations where you'd need to stop/disconnect the Redis client. A custom client is not sufficient because of the manual stopping. Here is the code I have thus far with using a custom client. Here is what I have thus far.

https://gist.github.com/idahogurl/6f5acd5205c132089eea96fd055b092d

Do you have a new or modified API suggestion to solve the problem?

Yes, #78 was closed but it can be done differently. ioredis supports clusters and if you pass in scaleReads it will treat the first Redis node as the primary and then the other as secondaries. To have our setup for a readonly you set scaleReads to slave

[Nargonath]

If I understand correctly, you want the option scaleReads to be passed to redis from the plugin options, don't you? Does it need any further development from this plugin to use such option or just passing it solves your problem? If the latter, have you tried passing it already? From what I can see here:

catbox-redis/lib/index.js

Line 41 in 8bb1c36

.unknown();

unknown keys are allowed in the Joi schema so you should be able to provide options that are not mentioned in catbox-redis documentation.

[idahogurl]

@Nargonath Thanks for the reply! I'll try it again. I attempted without and I got a validation error.

[idahogurl]

@Nargonath I tried with the latest package and it did work. Unfortunately we are not using @hapi/hapi@20. I cloned this repository and did a yarn link. It fails to connect but according to this redis/ioredis#1003 I have to be on the EC2 box. I will mark the issue as closed. We will have to do some upgrades. Thank you!!

[Nargonath]

You're welcome @idahogurl . I'm glad I could help. 😉