Skip to main content

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover.

I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves.

Master Node: (Centos 7.2) 192.168.1.11
Slave1 Node: (Centos 7.2) 192.168.1.12
Slave2 Node: (Centos 7.2) 192.168.1.13

Edit System settings on each node: /etc/sysctl.conf

Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub

Apply grub config and reboot each node:

Master Node: /etc/redis/6379.conf

Slave1 Node: /etc/redis/6379.conf

Slave2 Node: /etc/redis/6379.conf

Master Node: /etc/redis/sentinel.conf

Slave1 Node: /etc/redis/sentinel.conf

Slave2 Node: /etc/redis/sentinel.conf

Each Node: /etc/systemd/system/multi-user.target.wants/redis-server.service

Each Node: /etc/systemd/system/multi-user.target.wants/redis-sentinel.service

After creating service files reload systemd and enable,start related services on each node:

Check replication and sentinel status from redis-cli Master and slave nodes:
Master Node:

Slave Node:

Master Node:

Stop wait and start Redis Master and check logs on a slave:
Master Node:

Slave1 Node:

Now redis master is failed over another node.

Comments

  1. Thank you, for this post, It has helped me a lot, and very well explained

    ReplyDelete

Post a Comment

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter: