Timeout Issue with connection.async().clientSetname("lettuce#ClusterTopologyRefresh") Before Expected

[wmxl]

We've encountered an unexpected behavior in our monitoring system, which indicated an abnormal span as shown below:

This issue seems to arise within the io.lettuce.core.cluster.topology.DefaultClusterTopologyRefresh#openConnections method during the operation connection.async().clientSetname("lettuce#ClusterTopologyRefresh");.

Our current timeout setting is 300ms (for socketOptions) and 500ms (for connection and command), why the operation to set the client name results in a timeout exception after just 50ms?

[wmxl]

Hi @mp911de , could you provide some explanation about this?

[wmxl]

I think I figured it out. The reason is that we have different groups in the same server, which have different timeout configurations🤦 And one of them is 50ms.