Connection to redis cluster have much CLOSE_WAIT state

[jeevic]

Issue tracker is used for reporting bugs and discussing new features. Please use
stackoverflow for supporting issues.

in my production， i use go-redis visit redis cluster , i found much tcp close_wait

anyone fact this problem?

my go-redis version: v9.0.2

redis cluster time out 30s

i configuation go redis pool IdleTimeout 25s

Expected Behavior

low or none tcp close_wait

Current Behavior

much tcp close_wait

[monkey92t]

Is CLOSE_WAIT on the client(go-redis) or the server(redis-server cluster)?

[jeevic]

on the client side , i read go-redis source code find conn pool no Connection cleaning period， connection redis cluster initialized master and slave nodes client， default request to master node client。 the slave client no request， the server timeout will active close connection， the client in close wait

[monkey92t]

What are the PoolSize and MinIdleConns of your configuration connection pool?

go-redis doesn't create lots of connections, it only creates new connections when needed.

[jeevic]

PoolSize: 30
MinIdleConns:10

i use First In Last Out connnection mode， the front connection not visited ， the server exceed time will active close， but the client side not call close tcp channel the client side is close_wait, i think the connect need add keepalive heartbeat

[monkey92t]

Just 10 network connections, will cause a lot of close_wait?

[jeevic]

Just 10 network connections, will cause a lot of close_wait?

i connect to 5 redis cluster, each cluster have 48 nodes（24 master and 24 slave)。 by my count there are 1260 connections in CLOSE_WAIT

[monkey92t]

Oh..😂, this is a question worth thinking about.

[monkey92t]

1. When the salve node is not used (ReadOnly, RouteByLatency, RouteRandomly are not set), the salve-node uses the default connection pool configuration
2. Configure slave node connection pool configuration in ClusterOptions:

type ClusterOptions struct {
        PoolFIFO        bool
	PoolSize        int // applies per cluster node and not for the whole cluster
	PoolTimeout     time.Duration
	MinIdleConns    int
	MaxIdleConns    int
	ConnMaxIdleTime time.Duration
	ConnMaxLifetime time.Duration

        // add
        SlaveOption *Options
}

/cc @vmihailenco

[ndyakov]

Hello @jeevic , can you try with some of the latest releases? I am marking this for investigation, but don't know if I will have the time soon.

[jeevic]

Hello @jeevic , can you try with some of the latest releases? I am marking this for investigation, but don't know if I will have the time soon.

two years have passed. our Million-level concurrent system has been restructured based on Java. Due to the fact that most of golang libraries (etc log redis) we use have performance issues and we lack experience.

[ndyakov]

Understandable, thank you for your input.

…

On Mon, Jun 9, 2025 at 4:58 PM jeevi cao ***@***.***> wrote: *jeevic* left a comment (redis/go-redis#2447) <#2447 (comment)> Hello @jeevic <https://github.com/jeevic> , can you try with some of the latest releases? I am marking this for investigation, but don't know if I will have the time soon. two years have passed. our Million-level concurrent system has been restructured based on Java. Due to the fact that most of golang libraries (etc log redis) we use have performance issues and we lack experience. — Reply to this email directly, view it on GitHub <#2447 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALZXMUIIM2KY2GSF7MOLI33CWHGPAVCNFSM6AAAAAB6VJEFEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJVHA3TOMZZGQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Nedyalko Dyakov This email and any attachments may contain confidential and privileged information intended only for the recipient. If you are not the intended recipient, please notify the sender immediately, delete this email, and refrain from disclosing or using its contents. Unauthorized use, disclosure, or distribution of this communication is prohibited. Should you have any questions, please contact ***@***.***

[ndyakov]

Closing this for lack of information. If someone is experiencing the same, please feel free to open new issue.