Differences between revisions 16 and 23 (spanning 7 versions)
Revision 16 as of 2020-02-17 16:59:33
Size: 1666
Comment:
Revision 23 as of 2021-01-02 01:31:07
Size: 2215
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
DISCLAIMER
THIS ONLY WORKS IN BUSTER
Line 7: Line 9:
 * 192.168.1.58 redis01
 * 192.168.1.59 redis02
 * 192.168.1.60 redis03
 * 192.168.1.59 redis01
 * 192.168.1.60 redis02
 * 192.168.1.61 redis03
Line 14: Line 16:
apt-get install redis-server redis-sentinel apt-get install redis-server
Line 21: Line 23:
Make sure the apache servers can reach redis. Change `bind 127.0.0.1` in `/etc/redis/redis.conf`. Each of the redis servers needs to listen on its own IP-address. Change the contents of the redis configuration file in `/etc/redis/redis.conf`.
Line 23: Line 25:
Add the IP-address for each of the servers. Each of the redis servers needs to listen on its own IP-address.
Line 27: Line 30:
Stop the redis server on all hosts.
Enable redis to listen on the network, instead of only listening on the loopback device.
Line 29: Line 33:
service redis-server stop protected-mode no
Line 32: Line 36:
To enable replication we need to consider one of the redis servers the master. Here it will be redis01. On the two other hosts add the following to `/etc/redis/redis.conf`. Redis stores its data in memory only, hence its speed. To make sure redis does not loose its state, in case of a hardware failure, this will enable it to store the state as it changes in a file on disk.
Line 34: Line 38:
slaveof 192.168.1.58 6379 appendonly yes
Line 37: Line 41:
Start the redis servers again, but start it on redis01 first. Activate redis cluster features
Line 39: Line 43:
service redis-server start cluster-enabled yes
cluster-config-file nodes-6379.conf
cluster-node-timeout 15000
Line 41: Line 47:
redis01 should now be the master.
Line 43: Line 48:
=== Redis Sentinel === Restart the redis server on all hosts.
{{{
service redis-server restart
}}}
Line 45: Line 53:
The same goes for `/etc/redis/sentinel.conf` Next we will need to configure the servers to run as a cluster
Line 47: Line 55:
bind 127.0.0.1 192.168.1.58 redis-cli --cluster create 192.168.1.59:6379 192.168.1.60:6379 192.168.1.61:6379
Line 58: Line 66:
 * https://www.willandskill.se/en/setup-a-highly-available-redis-cluster-with-sentinel-and-haproxy/
 * https://www.tecmint.com/setup-redis-replication-in-centos-8/
 * https://www.tecmint.com/setup-redis-high-availability-with-sentinel-in-centos-8/
 * https://www.tecmint.com/setup-redis-cluster-in-centos-8/

DISCLAIMER THIS ONLY WORKS IN BUSTER INCOMPLETE DO NOT USE

Redis

Redis is an in memory data structure storage. It will be used to share PHP-sessions between the apache servers. To guarantee a robust deployment three redis servers will be configured.

  • 192.168.1.59 redis01
  • 192.168.1.60 redis02
  • 192.168.1.61 redis03

Software

apt-get install redis-server

Configuration

Redis Server

Change the contents of the redis configuration file in /etc/redis/redis.conf.

Add the IP-address for each of the servers. Each of the redis servers needs to listen on its own IP-address.

bind 127.0.0.1 192.168.1.58

Enable redis to listen on the network, instead of only listening on the loopback device.

protected-mode no

Redis stores its data in memory only, hence its speed. To make sure redis does not loose its state, in case of a hardware failure, this will enable it to store the state as it changes in a file on disk.

appendonly yes

Activate redis cluster features

cluster-enabled yes
cluster-config-file nodes-6379.conf
cluster-node-timeout 15000

Restart the redis server on all hosts.

service redis-server restart

Next we will need to configure the servers to run as a cluster

redis-cli --cluster create 192.168.1.59:6379 192.168.1.60:6379 192.168.1.61:6379

References

None: Redis (last edited 2022-01-03 22:09:21 by Kristian Kallenberg)