Adds a connection string (endpoint) to use while connecting to the redis server. Only the cluster mode will consider more than 1 element. If more are provided, they are not considered by the client when in single server mode.
Set the endpoints to use while connecting to the redis server. Only the cluster mode will consider more than 1 element. If more are provided, they are not considered by the client when in single server mode.
Sets a single connection string to use while connecting to the redis server. Will replace the previously configured connection strings.
Set the endpoints to use while connecting to the redis server. Only the cluster mode will consider more than 1 element. If more are provided, they are not considered by the client when in single server mode.
Set the master name (only considered in HA mode).
Tune how much nested arrays are allowed on a redis response. This affects the parser performance.
Tune the maximum size of the connection pool. When working with cluster or sentinel this value should be atleast the total number of cluster member (or number of sentinels + 1)
Tune the maximum waiting requests for a connection from the pool.
The client will always work on pipeline mode, this means that messages can start queueing. You can control how much backlog you're willing to accept. This methods sets how much handlers is the client willing to queue.
Set the net client options to be used while connecting to the redis server. Use this to tune your connection.
Set the default password for cluster/sentinel connections.
Tune how often in milliseconds should the connection pool cleaner execute.
For each connection in the pool, connections marked as invalid will be forcibly closed. A connection is marked invalid if it enters a exception or fatal state.
Set a user defined pool name (for metrics reporting).
Tune when a connection should be recycled in milliseconds.
Set the role name (only considered in HA mode).
Set the desired client type to be created.
Set whether or not to use replica nodes (only considered in Cluster mode).
Should the client perform REST protocol negotiation during the connection acquire.
By default this is true, but there are situations when using broken servers it may
be useful to skip this and always fallback to RESP2 without using the HELLO
command.
Sets a single connection string (endpoint) to use while connecting to the redis server. Will replace the previously configured connection strings.
Sets a single connection string to use while connecting to the redis server. Will replace the previously configured connection strings.
Set the endpoints to use while connecting to the redis server. Only the cluster mode will consider more than 1 element. If more are provided, they are not considered by the client when in single server mode.
Set the master name (only considered in HA mode).
Tune how much nested arrays are allowed on a redis response. This affects the parser performance.
Tune the maximum size of the connection pool. When working with cluster or sentinel this value should be atleast the total number of cluster member (or number of sentinels + 1)
Tune the maximum waiting requests for a connection from the pool.
The client will always work on pipeline mode, this means that messages can start queueing. You can control how much backlog you're willing to accept. This methods sets how much handlers is the client willing to queue.
Set the net client options to be used while connecting to the redis server. Use this to tune your connection.
Set the default password for cluster/sentinel connections.
Tune how often in milliseconds should the connection pool cleaner execute.
For each connection in the pool, connections marked as invalid will be forcibly closed. A connection is marked invalid if it enters a exception or fatal state.
Set a user defined pool name (for metrics reporting).
Tune when a connection should be recycled in milliseconds.
Should the client perform REST protocol negotiation during the connection acquire.
By default this is true, but there are situations when using broken servers it may
be useful to skip this and always fallback to RESP2 without using the HELLO
command.
Set the role name (only considered in HA mode).
Set the desired client type to be created.
Set whether or not to use replica nodes (only considered in Cluster mode).
Generated using TypeDoc
Redis Client Configuration options.