Lettuce redisclient how to#

Setting the requestQueueSize to a lower value will lead earlier to exceptions during overload or while the connection is in a disconnected state. The command invocation will lead to a RedisException if the queue size is exceeded. Reconnection can be activated again, but there is no public API to obtain the ConnectionWatchdog instance.Ĭontrols the per-connection request queue size. In contrast, where the protocol/connection activation fails due to SSL errors or PING before activating connection failure, queued commands are canceled. In case a connect timeout occurs, a connection reset, host lookup fails, this does not affect the cancellation of commands. The reconnect itself has two phases: Socket connection and protocol/connection activation. If this flag is true the reconnect will be suspended on protocol errors. See DecodeBufferPolicies for available strategies.įalse (was introduced in 3.1 with default true) Policy to discard read bytes from the decoding aggregation buffer to reclaim memory.

Lettuce redisclient how to#

Policy how to reclaim decode buffer memory In case a connect timeout occurs, a connection reset, host lookup fails, this does not affect the cancelation of commands. If this flag is true any queued commands will be canceled when a reconnect fails within the activation sequence.

SSL is natively supported by Lettuce and does no longer requires the use of SSL tunnels where protocol traffic can get out of sync. This flag is deprecated and should not be used as it can lead to race conditions and protocol offsets. This flag also has the effect that disconnected connections will refuse commands and cancel these with an exception. As soon as a connection gets closed/reset without the intention to close it, the client will try to reconnect, activate the connection and re-issue any queued commands. The PING handshake validates whether the other end of the connected socket is a service that behaves like a Redis server.Ĭontrols auto-reconnect behavior on connections. RESP 3/protocol discovery performs a HELLO handshake.įailed PING's on reconnect are handled as protocol errors and can suspend reconnection if suspendReconnectOnProtocolFailure is enabled. This option has no effect unless forced to use the RESP 2 protocol version. If the check fails, the connect/reconnect is treated as a failure.

If true (default is true), every connection and reconnect will issue a PING command and await its response before the connection is activated and enabled for use. Perform a lightweight PING connection handshake when establishing a Redis connection.