5 Seconds retry after connection lost about tomcat-cluster-redis-session-manager HOT 5 CLOSED

Hi @mmack,

This retry timing is internal to Jedis client and it's not configurable.

In the sentinel mode, the Jedis client will retry until a new Master node is elected by the Redis server. Also, if the Jedis client throws a connection exception, this session manager will retry 3 times every 2 seconds until the client receives a connection. So the probability of data loss is very less.

Thanks!

from tomcat-cluster-redis-session-manager.

It says "Sleeping 5000ms and retrying." and not 2 Seconds though... :)

from tomcat-cluster-redis-session-manager.

yes. 5000ms is internal to Jedis client.

If the current sentinel master node is not accessible/down, the Jedis client internally retries every 5000ms. If the runtime error in this process occurs, this session manager will retry 3 times every 2 seconds until the client gets the connection.

I hope it's clear now.

from tomcat-cluster-redis-session-manager.

FYI: #29

from tomcat-cluster-redis-session-manager.

Closing this issue. Please feel-free to reopen this issue/create new issue, if you require additional details in future.

from tomcat-cluster-redis-session-manager.