可能 redisTemplate.executePipelined 导致 SocketTimeOut

Could redisTemplate.executePipelined cause SocketTimeOut

这是我的代码:

redisTemplate.executePipelined(new SessionCallback<Object>() {
    @Override
    public Object execute(RedisOperations redisOperations) throws DataAccessException {
        redisTemplate.opsForSet().add(e, businessCode);
        return null;
    }
});

内码“redisTemplate.opsForSet().add(e, businessCode);”正在使用一个连接

感谢回答

补充栈错误信息:

org.springframework.data.redis.RedisConnectionFailureException: java.net.SocketTimeoutException: Read timed out; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketTimeoutException: Read timed out
    at org.springframework.data.redis.connection.jedis.JedisExceptionConverter.convert(JedisExceptionConverter.java:67)
    at org.springframework.data.redis.connection.jedis.JedisExceptionConverter.convert(JedisExceptionConverter.java:41)
    at org.springframework.data.redis.PassThroughExceptionTranslationStrategy.translate(PassThroughExceptionTranslationStrategy.java:37)
    at org.springframework.data.redis.FallbackExceptionTranslationStrategy.translate(FallbackExceptionTranslationStrategy.java:37)
    at org.springframework.data.redis.connection.jedis.JedisConnection.convertJedisAccessException(JedisConnection.java:241)
    at org.springframework.data.redis.connection.jedis.JedisConnection.zRange(JedisConnection.java:2348)
    at org.springframework.data.redis.connection.DefaultStringRedisConnection.zRange(DefaultStringRedisConnection.java:1058)
    at org.springframework.data.redis.core.DefaultZSetOperations.doInRedis(DefaultZSetOperations.java:101)
    at org.springframework.data.redis.core.DefaultZSetOperations.doInRedis(DefaultZSetOperations.java:98)
    at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:207)
    at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:169)
    at org.springframework.data.redis.core.AbstractOperations.execute(AbstractOperations.java:91)
    at org.springframework.data.redis.core.DefaultZSetOperations.range(DefaultZSetOperations.java:98)
    at com.*.mshop.reach.service.impl.ReachServiceImpl.query(ReachServiceImpl.java:178)
    at com.*.mshop.reach.service.impl.ReachServiceImpl$$FastClassBySpringCGLIB$3d23e1.invoke(<generated>)
    at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
    at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:667)
    at com.*.mshop.reach.service.impl.ReachServiceImpl$$EnhancerBySpringCGLIB$6aa953.query(<generated>)
    at com.*.mshop.facade.controller.ReachControllerImpl.query$original25E0bP(ReachControllerImpl.java:174)
    at com.*.mshop.facade.controller.ReachControllerImpl.query$original25E0bP$accessor$dcQnJrPQ(ReachControllerImpl.java)
    at com.*.mshop.facade.controller.ReachControllerImpl$auxiliary$jZ0njKo2.call(Unknown Source)
    at org.apache.skywalking.apm.agent.core.plugin.interceptor.enhance.InstMethodsInter.intercept(InstMethodsInter.java:86)
    at com.*.mshop.facade.controller.ReachControllerImpl.query(ReachControllerImpl.java)
    at com.*.mshop.facade.controller.ReachControllerImpl.queryCommodity$original25E0bP(ReachControllerImpl.java:203)
    at com.*.mshop.facade.controller.ReachControllerImpl.queryCommodity$original25E0bP$accessor$dcQnJrPQ(ReachControllerImpl.java)
    at com.*.mshop.facade.controller.ReachControllerImpl$auxiliary$NkOmWqfY.call(Unknown Source)
    at org.apache.skywalking.apm.agent.core.plugin.interceptor.enhance.InstMethodsInter.intercept(InstMethodsInter.java:86)
    at com.*.mshop.facade.controller.ReachControllerImpl.queryCommodity(ReachControllerImpl.java)
    at com.*.mshop.facade.controller.ReachControllerImpl$$FastClassBySpringCGLIB$$c8f1c1b6.invoke(<generated>)
    at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)

在此调用 executePipelined 的异常之前,大约 1 分钟,无法获得 redis 连接。

redis 连接池配置:

spring.redis.pool.max-active = 2000
spring.redis.pool.max-wait = 5000
spring.redis.pool.max-idle = 200
spring.redis.pool.min-idle = 10
spring.redis.timeout = 0

Redis Pipeline 对 Jedis 和 Lettuce 有不同的实现。

在 Jedis 中,管道将阻塞 1 个连接并使用相同的连接(bio)发送所有管道命令

在Lettuce中,管道使用Netty nio作为网络连接工具。所以管道在客户端执行的过程中,不会阻塞连接(一般lettuce会使用单连接)。当管道执行(发送到 Redis)时,它将 select 来自 Netty 的 1 个连接。

并且两个库都对管道命令使用相同的连接,因为它们将在单个网络请求中一起发送所有命令。