When using jedis and connecting redis in sentinel mode, Jedis Sentinel cannot operate without a pool. For details, please refer to JedisConnectionFactory.java#L713 and JedisSentinelPool.java
When using sentinel mode, spring-data-redis uses pooling by default. details is here
As a result, when the user sets spring.redis.jedis.pool.enabled=false and uses Jedis Sentinel Modeoperate Redis, the user will mistakenly think that spring-boot has made some efforts to make it closed under Jedis Sentinel Mode Pooling is implemented, but in fact it is not. The configuration in the default JedisPoolConfig will still be used internally.
Comment From: weixsun
I have the following solutions (but not limited to these). I don’t know which solution is most suitable for spring-boot’s appetite, so I want to hear the opinions of spring-boot core members and everyone.
1. Explain this situation directly in the reference.
2. Output a warning about this in the console at startup.
3. Use the startup failure analyzer to inform users that spring.redis.jedis.pool.enabled=false cannot be set in sentinel mode.
Comment From: wilkinsona
Thanks for raising this. I think we should align with Spring Data Redis's JedisClientConfiguration.JedisClientConfigurationBuilder.usePooling() and update the javadoc of the enabled property to explain that it only applies when using single node Redis and that pooling is implicitly enabled in sentinel mode.
Comment From: snicoll
Closing in favor of PR #27891