com.avsystem.commons.redis.config
ClusterConfig
Related Doc:
package config
function that returns NodeConfig given the address of the node.
function that returns ConnectionConfig for a monitoring connection used to monitor node with given address. The cluster client keeps single monitoring connection for every cluster master. Monitoring connections are used to refresh Redis Cluster state (current masters and slot mapping).
interval between routine cluster state refresh operations
minimal interval between consecutive cluster state refresh operations.
Normally, cluster state is not refreshed more frequently than specified by
autoRefreshInterval but additional refresh operations may be forced when
cluster redirections are observed. minRefreshInterval prevents too many
refresh operations from being executed in such situations.
function that determines how many randomly selected masters should be queried for cluster state during routine state refresh operation. The function takes current number of known masters as its argument.
RetryStrategy that controls Redis Cluster redirection handling
(MOVED and ASK responses).
RetryStrategy that controls retrying commands which failed with
TRYAGAIN error which may be returned for multikey commands during
cluster slot migration.
Delay after which RedisNodeClient is closed when it's master leaves cluster state (goes down or becomes a slave). Note that the node client is NOT operational during that delay. Trying to execute commands on it will result in NodeRemovedException
if RedisClusterClient has exactly one seed address configured and it points to a non-clustered Redis node then cluster client will not fail initialization but internally create a RedisNodeClient for that node and forward all operations to it.
interval between routine cluster state refresh operations
if RedisClusterClient has exactly one seed address configured and it points to a non-clustered Redis node then cluster client will not fail initialization but internally create a RedisNodeClient for that node and forward all operations to it.
minimal interval between consecutive cluster state refresh operations.
minimal interval between consecutive cluster state refresh operations.
Normally, cluster state is not refreshed more frequently than specified by
autoRefreshInterval but additional refresh operations may be forced when
cluster redirections are observed. minRefreshInterval prevents too many
refresh operations from being executed in such situations.
function that returns ConnectionConfig for a monitoring connection used to monitor node with given address.
function that returns ConnectionConfig for a monitoring connection used to monitor node with given address. The cluster client keeps single monitoring connection for every cluster master. Monitoring connections are used to refresh Redis Cluster state (current masters and slot mapping).
Delay after which RedisNodeClient is closed when it's master leaves cluster state (goes down or becomes a slave).
Delay after which RedisNodeClient is closed when it's master leaves cluster state (goes down or becomes a slave). Note that the node client is NOT operational during that delay. Trying to execute commands on it will result in NodeRemovedException
function that returns NodeConfig given the address of the node.
function that determines how many randomly selected masters should be queried for cluster state during routine state refresh operation.
function that determines how many randomly selected masters should be queried for cluster state during routine state refresh operation. The function takes current number of known masters as its argument.
RetryStrategy that controls Redis Cluster redirection handling
(MOVED and ASK responses).
RetryStrategy that controls retrying commands which failed with
TRYAGAIN error which may be returned for multikey commands during
cluster slot migration.
Configuration of a RedisClusterClient
function that returns NodeConfig given the address of the node.
function that returns ConnectionConfig for a monitoring connection used to monitor node with given address. The cluster client keeps single monitoring connection for every cluster master. Monitoring connections are used to refresh Redis Cluster state (current masters and slot mapping).
interval between routine cluster state refresh operations
minimal interval between consecutive cluster state refresh operations. Normally, cluster state is not refreshed more frequently than specified by
autoRefreshIntervalbut additional refresh operations may be forced when cluster redirections are observed.minRefreshIntervalprevents too many refresh operations from being executed in such situations.function that determines how many randomly selected masters should be queried for cluster state during routine state refresh operation. The function takes current number of known masters as its argument.
RetryStrategy that controls Redis Cluster redirection handling (
MOVEDandASKresponses).RetryStrategy that controls retrying commands which failed with
TRYAGAINerror which may be returned for multikey commands during cluster slot migration.Delay after which RedisNodeClient is closed when it's master leaves cluster state (goes down or becomes a slave). Note that the node client is NOT operational during that delay. Trying to execute commands on it will result in NodeRemovedException
if RedisClusterClient has exactly one seed address configured and it points to a non-clustered Redis node then cluster client will not fail initialization but internally create a RedisNodeClient for that node and forward all operations to it.