Redis Version: 7.2.3 OS: Rocky Linux release 8.8 Redis Mode: Standalone Configuration: 5 nodes with sentinel running on each Jedis version: 3.1.0
Java applications are facing read timeout issues after upgrading Redis from 6.2.6 to 7..2.3. Number of keys also increased from 2 million to 4.5 million.
Issue is intermittent, we keep getting below errors in logs:
2023-11-21 14:33:16.744
| ERROR | [XNIO-1 task-4] | c.d.commongraphql.db.RedisDataStore | Exception while getting getResourceCache: redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out
2023-11-21 02:45:17.768
| ERROR | [XNIO-1 task-3] | c.d.commongraphql.db.RedisDataStore | Exception while getting getResourceCache: redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool
at redis.clients.jedis.util.Pool.getResource(Pool.java:59)
Timeout is disabled from Redis server end. On application end, we're using default timeout.
We're running the same query as before, could this be because of heavy load on Redis?
We checked latency using memtier_benchamrk and got below results:
Below is the configuration we used for the test:
4 Threads
50 Connections per thread
10000 Requests per client
Comment From: enjoy-binbin
Redis from 6.2.6 to 7..2.3.
can you try 7.0? From 6.2 directly to 7.2, the span may be quite large