redis application level keep alive

[chenjuq126]

Feature Request

Lettuce cannot recover from connection problems. The problem is fixed.

My condition differs from it a little: a socks proxy add between client and redis. lettuce <--> socks proxy A <--> redis server lettuce <--> socks proxy B <--> redis server

Is there any application feature for client to detect server alive or reachable? Because, SocketOptions and EpollChannelOption.TCP_KEEPINTVL works on TCP layer. 1 if there is a TCP socks proxy between lettuce and redis server； 2 the TCP keep-alive data packet can not be transferred to redis server； 3 if socks proxy A can not reach redis server temporary eg. 20 minutes. on the 3 items above, clients connected with A can not know whether the server is reachable in a short time, if only depends on TCP keep-alive. setget, pubsub, and lock can not work.

Is your feature request related to a problem? Please describe

A clear and concise description of what the problem is. Ex. I have an issue when [...]

Describe the solution you'd like

Application level keep alive configuration.

A clear and concise description of what you want to happen. Add any considered drawbacks.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Teachability, Documentation, Adoption, Migration Strategy

If you can, explain how users will be able to use this and possibly write out a version the docs. Maybe a screenshot or design?