OCF_HEARTBEAT_REDIS(7) | OCF resource agents | OCF_HEARTBEAT_REDIS(7) |
ocf_heartbeat_redis - Redis server
redis [start | stop | status | monitor | promote | demote | meta-data | validate-all]
Resource agent script for redis server.
This resource fully supports master/slave replication. The master preference of a node is determined by the 'slave_priority' parameter of the redis config. When taking the resource from 'unmanaged' to 'managed', the currently active master will be given a priority of 1000 (plus 1 for each active connection). The default 'slave_priority' is 100, so the master will stay master. For a slave to become master after converting the resource to managed, set a slave_priority greater than 1000.
bin
(optional, string, default "/usr/bin/redis-server")
client_bin
(optional, string, default "/usr/bin/redis-cli")
config
(unique, optional, string, default "/etc/redis/redis.conf")
user
(optional, string, default "redis")
rundir
(unique, optional, string, default "/var/run/redis")
pidfile_name
(optional, string, default "redis-server.pid")
socket_name
(optional, string, default "redis.sock")
port
(optional, string, default "6379")
tunnel_host
Note that in order to enable replication traffic tunneling, parameter {tunnel_port_map} must be populated.
(optional, string, default "127.0.0.1")
tunnel_port_map
To be used when redis servers need to tunnel replication traffic. On every node where the redis resource is running, the redis server listens to a different port. Each redis server can access its peers for replication traffic via a tunnel accessible at {tunnel_host}:port.
The mapping the form of: pcmk1-name:port-for-redis1;pcmk2-name:port-for-redis2;pcmk3-name:port-for-redis3
where the redis resource started on node pcmk1-name would listen on port port-for-redis1
(optional, string, no default)
wait_last_known_master
(optional, boolean, default false)
This resource agent supports the following actions (operations):
start
stop
status
monitor
monitor (Master role)
monitor (Slave role)
promote
demote
notify
validate-all
meta-data
The following is an example configuration for a redis resource using the crm(8) shell:
primitive p_redis ocf:heartbeat:redis \
op monitor depth="0" timeout="60s" interval="45s" \
op monitor role="Master" depth="0" timeout="60s" interval="20s" \
op monitor role="Slave" depth="0" timeout="60s" interval="60s"
ms ms_redis p_redis \
meta notify="true" interleave="true"
The following is an example configuration for a redis resource using pcs(8)
pcs resource create p_redis ocf:heartbeat:redis \
op monitor depth="0" timeout="60s" interval="45s" \
op monitor role="Master" depth="0" timeout="60s" interval="20s" \
op monitor role="Slave" depth="0" timeout="60s" interval="60s" --master
http://clusterlabs.org/
ClusterLabs contributors (see the resource agent source for information about individual authors)
06/27/2020 | resource-agents UNKNOWN |