How to use Conductor with Standalone Redis cache which has timeout for idle connections.

[vamsibandarupalli]

I was trying to use conductor with Azure Cache for Redis, which has 10 minutes timeout for idle connections. Conductor was priming 31 connections when started the server and at some point if there are no (read/write)operations performed to redis, Azure is terminating the idle connections as a result getting the broken pipe error.

Also in Conductor documentation it is mentioned maxConnectionPerHost as 31 is there any reason it should be 31? If we decrease it will there be any decrease in performance?

[aravindanr]

I am not sure how the timeout for idle connections and the maxConnectionPerHost are connected. The error you described is related to connections timing out and maxConnectionPerHost controls the number of connections per host.

[vamsibandarupalli]

Hi, those are two different questions, not connected.

1. How to use Conductor with Redis Cache which has timeout for idle connections.
2. Is there any specific reason for maxConnectionPerHost to be 31? Or is it just a random number added in the docs here

[aravindanr]

Understood.

1. Conductor does not expose a property to modify connection timeout values for Redis. But RedisClusterConfiguration can be modified to include a timeout property. If you are inclined, please create a PR.
2. It's the latter. It's a number that we internally used at some point and not a mandate. The default value is 10 and it could be set to any desired value.