ClusterConnectionProvider might cause TCP connection leak

[970655147]

this is a project using spring-data-redis, spring-boot-actuator
there are 2 case, might reoccur that

1. config address that isn't redis server, follow try a mysql services,
   then visit "http://localhost:8080/actuator/health", there leak 6 tcp connection each visit
   spring.redis.cluster.nodes: 192.168.220.133:3306,192.168.220.133:3307,192.168.220.133:3308,192.168.220.133:3309,192.168.220.133:3310,192.168.220.133:3311

2. config redis server with password, but didn't config "spring.redis.password"
   then visit "http://localhost:8080/actuator/health", there leak 6 tcp connection each visit
   spring.redis.cluster.nodes: 192.168.220.133:7001,192.168.220.133:7002,192.168.220.133:7003,192.168.220.133:7004,192.168.220.133:7005,192.168.220.133:7006

use "ll /proc/$pid/fd | grep socket" to watch connections

[jxblum]

Actuator is part of Spring Boot, not Spring Data Redis.

[970655147]

but core code is in spring-data-redis, main context in LettuceConnectionFactory$SharedConnection.getConnection
if ClusterConnectionProvider.getConnection throw Exception, there maybe tcp connection leak
spring-boot-acurator is just a trigger in this context

[970655147]

but core code is in spring-data-redis, main context in LettuceConnectionFactory$SharedConnection.getConnection
if ClusterConnectionProvider.getConnection throw Exception, there maybe tcp connection leak
spring-boot-acurator is just a trigger in this context

[970655147]

Actuator is part of Spring Boot, not Spring Data Redis.

sorry, my presentation is not exactly
but core code is in spring-data-redis, main context in LettuceConnectionFactory$SharedConnection.getConnection
if ClusterConnectionProvider.getConnection throw Exception, there maybe tcp connection leak
spring-boot-acurator is just a trigger in this context

[jxblum]

Let me review and evaluate this further.

[jxblum]

Closed by mistake.