When the lettuce cannot connect to the Redis server, it feels like serial execution

[ChenYingqin]

Bug Report

maybe related：#2082

Current Behavior

When unable to connect to the Redis server, as the concurrency of the lettuce load test increases, the throughput rate will not change much, but the response time will increase exponentially

Using lettuce to connect to a port that is not a Redis service to simulate a timeout issue caused by Redis server hardware problems that prevent lettuce from connecting to the server. There is a strange phenomenon here, and I don't know what's going on. Can anyone help me? When I use 1 concurrent to perform stress testing on a web service, the QPS is 0.8. However, with 10 concurrent tests, QPS sometimes remains at 0.8. We know that lettuce is non blocking, and theoretically QPS should be 8

Screenshot of Test Records：

Stack trace

// your stack trace here;

[lettuce-epollEventLoop-926-1] [i.l.c.c.t.DefaultClusterTopologyRefresh][344] - Unable to connect to [10.178.16.245:6380]: java.nio.channels.ClosedChannelException
io.lettuce.core.RedisConnectionException: Unable to establish a connection to Redis Cluster
at io.lettuce.core.cluster.RedisClusterClient.lambda$assertInitialPartitions$26(RedisClusterClient.java:955)
at io.lettuce.core.cluster.RedisClusterClient.get(RedisClusterClient.java:974)
at io.lettuce.core.cluster.RedisClusterClient.assertInitialPartitions(RedisClusterClient.java:954)
at io.lettuce.core.cluster.RedisClusterClient.connect(RedisClusterClient.java:406)
at io.lettuce.core.cluster.RedisClusterClient.connect(RedisClusterClient.java:383)

Input Code

Input Code

// your code here;

Expected behavior/code

Environment

• Lettuce version(s): 6.5.1.RELEASE

Possible Solution

Additional context

[ChenYingqin]

i know the reason,each call requires the use of a different reactive connection

[tishun]

@ChenYingqin let me know if you need further assistance.