IBM Aspera HST Admin Manual page 308

2. On the Redis primary node, create (or edit an existing) /opt/aspera/etc/redis.conf with the following
values:
bind private_ip_address
port 31415
daemonize yes
pidfile /opt/aspera/var/run/redis.31415.pid
/opt/aspera/var/run/redis_31415.log
tcp-keepalive 300
dbfilename /opt/aspera/var/redis.31415.rdb
dir /opt/aspera/var
save 900 1
protected-mode no
Where private_ip_address is the private IP address of the node.
Note: If you want Redis to use the system logger, comment out /opt/aspera/var/run/
redis_31415.log and set syslog-enabled to yes. For example:
#/opt/aspera/var/run/redis_31415.log
syslog-enabled yes
Configure other syslog parameters, if desired.
Save your changes and close the file.
3. On the Redis replica nodes, create (or edit an existing) /opt/aspera/etc/redis.conf with the following
values:
slave of primary_ip_address 31415
bind private_ip_address
port 31415
daemonize yes
pidfile /opt/aspera/var/run/redis.31415.pid
/opt/aspera/var/run/redis_31415.log
tcp-keepalive 300
dbfilename /opt/aspera/var/redis.31415.rdb
dir /opt/aspera/var
save 900 1
protected-mode no
Where:
• primary_ip_address is the private IP address of the primary node
• private_ip_address is the private IP address of the local replica node
Configure logging as you did on the primary node.
Save your changes and close the file.
4. On each node, configure Redis Sentinel.
a) Open port 26379 in iptables.
b) Open /opt/aspera/etc/sentinel.conf and add or edit the following lines:
port 26379
bind private_ip_address
sentinel monitor primary_name primary_ip_address 31415 quorum
sentinel down-after-milliseconds primary_name down_time
sentinel failover-timeout primary_name timeout
logfile "/opt/aspera/etc/redis-sentinel.log"
Where:
#turn off password protection
#turn off password protection
| Highly-Available Redis Backend for an HST Server Cluster | 308