Option to reduce connection churn #261

Activity

1. sonus21 commented on Jul 17, 2025

   

   sonus21

   on Jul 17, 2025

   Owner

   More actions

   do you've any metrics at server level to identify how many connections it has established? Rqueue does not consume connection properties from the application.properties/yaml file. You can try to create and supply a new connection factory manually.
2. fydelity commented on Jul 24, 2025

   

   fydelity

   on Jul 24, 2025

   Author

   More actions

   My theory was that during spikes I enqueue a large amount of messages at once. On spikes I had 2000 messages in my first queue, and those fan out 100x to 200000 of new messages in a short amount of time). And rqueue opened up channels to write each messages but did not closed fast enough to allow us to open. The error rate I received from the timeout disappear when I followed your suggestion and wrote this bean. I can't tell for sure that this was the solution, but the error rate went down from once an hour (on spikes) to zero an hour. It is hard for me to think that Im the first one to encounter this issue, which makes me question my assumptions. My real question is, can we allow enqueueAll that uses the same channel?

   This was my solution to limit the connetions:

   @Bean
     public LettuceConnectionFactory redisConnectionFactory(Environment env) {
       String host = env.getProperty("spring.data.redis.host");
       int port = Integer.parseInt(env.getProperty("spring.data.redis.port", "0"));
       String username = env.getProperty("spring.data.redis.username");
       String password = env.getProperty("spring.data.redis.password");
   
       RedisStandaloneConfiguration serverConfig = new RedisStandaloneConfiguration(host, port);
       serverConfig.setUsername(username);
       serverConfig.setPassword(RedisPassword.of(password));
   
       GenericObjectPoolConfig<?> poolConfig = new GenericObjectPoolConfig<>();
       poolConfig.setMaxTotal(20);
       poolConfig.setMaxIdle(10);
       poolConfig.setMinIdle(5);
       poolConfig.setMaxWait(Duration.ofSeconds(10));
   
       LettucePoolingClientConfiguration clientConfig =
           LettucePoolingClientConfiguration.builder()
               .poolConfig(poolConfig)
               .commandTimeout(Duration.ofSeconds(30))
               .shutdownTimeout(Duration.ofSeconds(5))
               .build();
       LettuceConnectionFactory factory = new LettuceConnectionFactory(serverConfig, clientConfig);
       factory.setShareNativeConnection(false);
       factory.afterPropertiesSet();
       return factory;
     }
3. sonus21 commented on Jul 24, 2025

   

   sonus21

   on Jul 24, 2025

   Last edited by sonus21

   Owner

   More actions

   That’s an interesting observation, though I’m not entirely sure what you mean by channel in this context. Could you share a more complete stack trace? That would help in identifying where exactly the failure is occurring whether it's during enqueue, processing, or in the message handler.

   It's possible that the solution you applied has temporarily resolved the issue, but if there's an underlying problem with Rqueue, this fix may not hold up under different conditions.

   Could you try running a load test to see if the issue reappears, even after setting the pool?
4. sonus21

   added

   more information requiredMore information requiredMore information required

   on May 3, 2026