Jedis behavior during Elasticache redis failover

130 views
Skip to first unread message

Julian Medina

unread,
Oct 11, 2021, 7:01:43 AM10/11/21
to Jedis
Hello all -

During a planned or actual failover scenario in elasticache redis we're experiencing the following behavior.

Jedis switches to new primary node (at a very poor performance level creating thousands of new connections and spitting out large amounts of errors), e.g.
  • redis.clients.jedis.exceptions.JedisClusterOperationException: Cluster retry deadline exceeded.
  • redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out
  • redis.clients.jedis.JedisFactory: Error while close

And after recovery of the original primary node jedis continue to create thousands of connections with the secondary failover node without ever recovering the original performance.

Julian Medina

unread,
Oct 11, 2021, 11:08:50 AM10/11/21
to Jedis
Duplicate from other thread, feel free to delete.
Reply all
Reply to author
Forward
0 new messages