OCF_HEARTBEAT_REDIS(7)
π ocf_heartbeat_redis β Redis server π
okay bestie, you're reading OCF_HEARTBEAT_REDIS(7), the manual page for ocf_heartbeat_redis from the OCF resource agents crew. This is your full tour, no cap, no skipped details. π
π NAME π
ocf_heartbeat_redis β Redis server. That's the name, that's the vibe, periodt. β¨
β¨ SYNOPSIS β¨
The action menu is literally:
redis [start | stop | status | monitor | promote | demote | meta-data |
validate-all]
πΈ DESCRIPTION πΈ
Resource agent script for redis server. It's giving infrastructure realness. π
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 slave_priority greater than 1000. π
π SUPPORTED PARAMETERS π
Here's every knob and default, zero skipped, fr fr:
binβ Path toredis-server(optional, string, default"/usr/bin/redis-server")client_binβ Path toredis-cli(optional, string, default"/usr/bin/redis-cli")configβ Path toredis.conf(unique, optional, string, default"/etc/redis/redis.conf")userβ User to run redis as (optional, string, default"redis")rundirβ Directory to store socket and pid file in (unique, optional, string, default"/var/run/redis")pidfile_nameβ The filename to use for the pidfile. Will be created in the rundir. Should only be a basename, not a full path. (optional, string, default"redis-server.pid")socket_nameβ The filename to use for the socket. Will be crated in the rundir. Should only be a basename, not a full path. (optional, string, default"redis.sock") β yes, βcratedβ is the original spelling, we respect the icon πportβ Port for replication client to connect to on remote server (optional, string, default"6379")tunnel_hostβ When replication traffic is tunnelled, this is the host to target to forward outgoing traffic to the redis master. The resource agent configures the redis slave to target the master viatunnel_host:tunnel_port. 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β A mapping of pacemaker node names to redis port number. 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 has the form of:pcmk1-name:port-for-redis1;pcmk2-name:port-for-redis2;pcmk3-name:port-for-redis3where the redis resource started on nodepcmk1-namewould listen on portport-for-redis1(optional, string, no default)wait_last_known_masterβ During redis cluster bootstrap, wait for the last known master to be promoted before allowing any other instances in the cluster to be promoted. This lessens the risk of data loss when persistent data is in use. (optional, boolean, defaultfalse)
π¦ SUPPORTED ACTIONS π¦
This resource agent supports the following actions (operations):
startβ Starts the resource. Suggested minimum timeout:120s.stopβ Stops the resource. Suggested minimum timeout:120s.statusβ Performs a status check. Suggested minimum timeout:60s.monitorβ Performs a detailed status check. Suggested minimum timeout:60s. Suggested interval:45s.monitor (Promoted role)β Performs a detailed status check. Suggested minimum timeout:60s. Suggested interval:20s.promoteβ Promotes the resource to the Master role. Suggested minimum timeout:120s.demoteβ Demotes the resource to the Slave role. Suggested minimum timeout:120s.notifyβ Suggested minimum timeout:90s.validate-allβ Performs a validation of the resource configuration. Suggested minimum timeout:5s.meta-dataβ Retrieves resource agent metadata (internal use only). Suggested minimum timeout:5s.
π EXAMPLE CRM SHELL π
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="Promoted" depth="0" timeout="60s" interval="20s"
ms ms_redis p_redis \
meta notify="true" interleave="true"
π EXAMPLE PCS π
The following is an example configuration for a redis resource using pcs(8):
pcs resource create p_redis ocf:heartbeat:redis \
op monitor OCF_CHECK_LEVEL="0" timeout="60s" interval="45s" \
op monitor role="Promoted" OCF_CHECK_LEVEL="0" timeout="60s" interval="20s" promotable
β SEE ALSO β
The one and only listed link is literally http://clusterlabs.org/ β go look, bestie. β¨
π AUTHOR π
ClusterLabs contributors (see the resource agent source for information about individual authors) π
byeeee bestie β this iconic page is from resource-agents UNKNOWN, dated 10/01/2026 π
π¦ where this page comes from
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- opensuse-leap 16.0: resource-agents 4.18.0+git105.9ea1183-160000.1.1 Β· GPL-2.0-only AND LGPL-2.1-or-later AND GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms