After a machine in the Redis cluster crashes, a large number of RedisClusterNode instances will be created in the service, but they cannot be recycled, resulting in the service being continuously full GC

[yuanyunlu]

Current Behavior

hi @mp911de ,
In the production environment, a Redis machine crashed and the service successfully enabled the topology refresh function. One day later, our machine had not yet recovered, but the service experienced high CPU. After analyzing the heap dump files, it was found that a large number of RedisClusterNode objects were created, and the JVM was unable to recycle them, resulting in a continuous full GC. I would like to know why. thanks

Environment

• Spring-boot： [2.3.2.RELEASE]
• Lettuce version(s): [5.3.2.RELEASE]
• Redis version: [6.2.6]

Additional context

This is the image analyzed by jprofiler

[mp911de]

If you have a heap dump handy, please investigate the GC roots of the held object. It can well be that some of these objects are held by retry instances or other ones that are attached to objects that aren't cleared.