bodong.ybd

> Redis command throws timeout exception (which is okay), And it's never detectable such unhealthy. Theoretically, TCP retransmission will occur at this time, and the default will end after [924.6...

@wpstan You can't `Schedule Task ping redis` in `another thread` or a `new connection`, you can only choose an existing connection in netty, otherwise you won't be able to recover...

> It recommends setting keepalive parameters for the underlying TCP connection. If the JDK version used is less than 11，Netty Epoll dependencies need to import. @wpstan keepalive is only valid...

@mp911de > Disconnecting the connection upon command timeout is a pretty drastic approach that can work in certain scenarios in which you cannot customize retransmit parameters. yes, adjusting parameters such...

> I think it makes sense to host such a feature (disconnect on timeout) within `TimeoutOptions`. Agreed, but I think a better strategy is to reconnect after X (1 by...

> I think a better strategy is to reconnect after X (1 by default) `consecutive timeouts` I mean from X `consecutive` timeouts, if x = 2, the sequence should be:...

> > I think a better strategy is to reconnect after X (1 by default) `consecutive timeouts` > > I mean from X `consecutive` timeouts, if x = 2, the...

> @yangbodong22011 How's the PR going :) We need this mechanism badly. Waiting for @mp911de to have time to process it, we don't have a firm strategy yet.

> I like the idea. However, the 1st option will lock us into single-key ZRANK forever. @itamarhaber Are you thinking of a command like `zmrank`? Is it right? Will it...

I think implementing two commands is **easy to understand** and **friendly to client developers**: ```` z[rev]rank key member [withscore] zm[rev]rank key 3 member1 member2 member2 [withscore] ````