Shulou(Shulou.com)06/02 Report--

Master-slave mode

Redis master-slave mode, as the name implies. That is, "one master, one slave" or "one master and multiple followers". The configuration is simple, only need to write a parameter in the configuration file of the slave.

Slaveof # for example # slaveof 192.168.1.197 6379

Advantages:

It has the advantages of simple configuration, flexible use and high data security.

Disadvantages:

Unable to achieve failover, when master down, slave cannot automatically switch over to take over subsequent tasks.

Sentinel mode

The deployment steps of Sentinel mode are also very simple, and the redis.conf configuration file is not described. Just like the normal redis configuration file, cp is fine.

/ / vim sentinel.conf# backend runs ip, a server bound to protected-mode yes#. If IP is not written and defaults to 127.0.0.1, you can only connect locally to bind 10.10.10.13 and run daemonize yes# in the background to open the port. If the master and slave are all on the same machine, remember to change the port. Do not conflict with the ip address and port of the master to be monitored by port 2638. The following 1 indicates that a sentry discovers master down. Switching slave to mastersentinel monitor mymaster 127.0.0.1 6379 master sentinel will send a heartbeat PING to master to confirm whether the master is alive. If the master does not respond to the PING within a "certain time range" or replies to an error message, # then the sentinel will subjectively (unilaterally) assume that the master is no longer available (subjectively down, also referred to as SDOWN). # and this down-after-milliseconds is used to specify this "certain time range", in milliseconds. Sentinel down-after-milliseconds mymaster 300 years failover expiration time. When the failover starts, no failover operation is triggered within this time, and the current sentinel will consider the failoer failed. Sentinel failover-timeout mymaster 1800

Start the redis process and the sentinel process respectively.

. / redis-server redis.conf./redis-server sentinel.conf

Highly available cluster fragmentation mode

It is important to explain how redis's official cluster installation works.

The software you need to use

Redis-4.0.9.tar.gz download (cluster feature is supported since 3. 0)

Ruby-2.5.7.tar.gz download (generally, we can choose 2.4or2.5. try not to use yum installation, because the ruby installed by yum is 2.0.0, and the version of gem install redis ruby must be 2.2.2 or above)

Redis-4.0.0.gem download

Zlib-1.2.11.tar.gz searches on the Internet by itself.

Openssl-1.1.1a.tar.gz searches on the Internet by itself.

Startup port: 7001 7002 7003 7004 7005 7006

Configuration file: / app/redis/redis-cluster

In this paper, we build a Redis cluster with 6 nodes on one Linux (in the actual production environment, 3 Linux servers are required to store 3 Master)

Use root user installation, because ordinary users do not have permission to create directories and compile, so authorization is required

The following are only the offline installation steps

Installation

Step 1: install the gcc environment

Check the gcc version. If there is no installation, you need to install it.

[root@localhost ~] # gcc-v uses built-in specs. Goal: x86_64-redhat-linux is configured as:.. / configure-- prefix=/usr-- mandir=/usr/share/man-- infodir=/usr/share/info-- with-bugurl= http://bugzilla.redhat.com/bugzilla-- enable-bootstrap-- enable-shared-- enable-threads=posix-- enable-checking=release-- with-system-zlib-- enable-__cxa_atexit-- disable-libunwind-exceptions-- enable-gnu-unique-object-- enable-languages=c,c++,objc,obj-c++,java,fortran Ada-enable-java-awt=gtk-disable-dssi-with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre-enable-libgcj-multifile-enable-java-maintainer-mode-with-ecj-jar=/usr/share/java/eclipse-ecj.jar-disable-libjava-multilib-with-ppl-with-cloog-with-tune=generic-with-arch_32=i686-build=x86_64-redhat- Linux line Program model: posixgcc version 4.4.7 20120313 (Red Hat 4.4.7-23) (GCC)

Install online using the yum command

Yum-y install gcc gcc-c++

Step 2: extract redis and compile and install

Cd / app/redis/tar-xvf redis-4.0.9.tar.gzcd redis-4.0.9/make/app/redis/redis-4.0.9/srcmake install

Prompt for successful installation

Hint: It's a good idea to run 'make test';) INSTALL installINSTALL installINSTALL installINSTALL installINSTALL install

After redis is installed, there will be several more files in the / usr/local/bin directory.

[root@localhost] # ll / usr/local/bin total dosage 35500-rwxr-xr-x. 1 root root 5600238 May 6 20:54 redis-benchmark-rwxr-xr-x. 1 root root 8331277 May 6 20:54 redis-check-aof-rwxr-xr-x. 1 root root 8331277 May 6 20:54 redis-check-rdb-rwxr-xr-x. 1 root root 5739834 May 6 20:54 redis-clilrwxrwxrwx. 1 root root 12 May 6 20:54 redis-sentinel-> redis-server-rwxr-xr-x. 1 root root 8331277 May 6 20:54 redis-server

Step 3: extract ruby and compile and install

Cd / app/redistar-xvf ruby-2.5.1.tar.gzcd ruby-2.5.1/./configure-- prefix=/usr/local/ruby-- prefix installs ruby to a specified directory, or you can customize make & & make install

After successful installation, you can see that there are four more directories in the ruby directory.

[root@localhost] # ll / usr/local/ruby total dosage 16drwxr-xr-x. 2 root root 4096 October 10 11:59 bindrwxr-xr-x. 3 root root 4096 October 10 11:59 includedrwxr-xr-x. 4 root root 4096 October 10 11:59 libdrwxr-xr-x. 5 root root 4096 October 10 11:59 share

Configure ruby environment variables

Vi / etc/profileexport PATH=$PATH:/usr/local/ruby/bin:wqsource / etc/profileecho $PATH/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/openssh-7.5p1/bin:/root/bin:/usr/local/ruby/bin

View the ruby version number

[root@localhost] # ruby-vruby 2.5.7p206 (2019-10-01 revision 67816) [x86_64-linux]

Step 4: create the redis-cluster cluster directory and copy the gem package of redis and copy the redis-trib.rb cluster management tools to the cluster directory under src

Cd / app/redismkdir redis-clustercp redis-4.0.0.gem redis-cluster//app/redis/redis-4.0.9/srccp redis-trib.rb / app/redis/redis-cluster/

Step 5: install redis's gem package using gem

Cd / app/redis/redis-clustergem install redis-4.0.0.gem

If there is no problem with the installation, the following prompt appears

Successfully installed redis-4.0.0Parsing documentation for redis-4.0.0Installing ri documentation for redis-4.0.0Done installing documentation for redis after 1 seconds1 gem installed

If you report an error in step 5, you need zlib or openssl

Solve the problem of zlib error

Cd / app/redis/ruby-2.5.1/ext/zlibruby extconf.rb-creating Makefilecreating Makefile will appear after success-if creating Makefile does not appear Execute the following command ruby extconf.rb-- with-zlib-dir=/usr/local/zlib/vi Makefile to change zlib.o: $(top_srcdir) / include/ruby.h to zlib.o:.. /.. / include/ruby.hmake# successfully display linking shared-object zlib.somake install# successfully display / usr/bin/install-c-m 0755 zlib.so / usr/local/ruby/lib/ruby/site_ruby/2.5.0/ X86_64-linux, if you do not modify the Makefile before executing the make above The following error make will be reported: * No rule to make target / include/ruby.h', needed byzlib.o'. Stop.

Solve the problem of openssl error

First, install openssl. If the system is installed, this step can be omitted.

Cd / app/redistar-zxvf openssl-1.1.1a.tar.gz./config-- prefix=/usr/local/openssl & & make & & make install

Continue to resolve the openssl error problem after the installation is complete

Cd / app/redis/ruby-2.5.1/ext/opensslruby extconf.rb-creating Makefile will appear after success

If no creating Makefile is found, execute the following command

Vi Makefile modifies all $(top_srcdir) to.. /.. $(top_srcdir) # Note (top_srcdir) there is more than one All have to change make# successfully install output linking shared-object openssl.somake install# successfully install output / usr/bin/install-c-m 0755 openssl.so / usr/local/ruby/lib/ruby/site_ruby/2.5.0/x86_64-linuxinstalling default openssl libraries if the above does not modify Makefile before executing make, it will report the following error make: * No rule to make target / include/ruby.h', needed byossl.o'. Stop.

Use gem to install redis's gem package again

# you can install cd / app/redis/redis-clustergem install redis-4.0.0.gem without accident

four。 Create a cluster

As mentioned earlier, we need 6-node Redis as a cluster, so we need to create 6 folders to store the configuration information of 6 nodes, and 6 nodes need to correspond to 6 port numbers, such as 7001-7006. We can define this port number ourselves.

/ app/redis/redis-cluster/mkdir 700 {1, 2, 3, 4, 5, 5, 6}-create six folders in batch

Copy the configuration file redis.conf from the original redis installation directory to the six newly created folders

Cd / app/redis/redis-4.0.9cp redis.conf / app/redis/redis-cluster/7001/cp redis.conf / app/redis/redis-cluster/7002/cp redis.conf / app/redis/redis-cluster/7003/cp redis.conf / app/redis/redis-cluster/7004/cp redis.conf / app/redis/redis-cluster/7005/cp redis.conf / app/redis/redis-cluster/7006/

Copy the server and client generated after redis installation to the six newly created folders

Cd / usr/local/bin/cp redis-server redis-cli / app/redis/redis-cluster/7001/cp redis-server redis-cli / app/redis/redis-cluster/7002/cp redis-server redis-cli / app/redis/redis-cluster/7003/cp redis-server redis-cli / app/redis/redis-cluster/7004/cp redis-server redis-cli / app/redis/redis-cluster/7005/cp redis-server redis-cli / app/redis/redis-cluster/7006/

Modify some parameters of the configuration file redis.conf under the newly created six folders

Cd / app/redis/redis-cluster/ modifies redis.confbind 192.168.5.104 in 7001-7006 to connect to the ip address of the host. Port 700x is the folder name in your redis cache server without modifying the external connection. Enter a few daemonize yes in your 700s to turn on daemon mode. In this mode, redis runs in the background and writes the process pid number to the file set by the redis.conf option pidfile, and redis runs all the time unless you manually kill the process. Pidfile / app/redis/redis-cluster/700x/redis_700x.pid x is the name of the folder. You can start cluster mode by filling in a few cluster-enabled yes in your 700s.

Cd / app/redis/redis-cluster

Write a batch vim start-all.sh and use vi if vim doesn't support it.

Vim start-all.sh

Cd 7001. / redis-server redis.confcd.. cd 7002. / redis-server redis.confcd.. cd 7003. / redis-server redis.confcd.. cd 7004. / redis-server redis.confcd.. cd 7005. / redis-server redis.confcd.. cd 7006. / redis-server redis.confcd.. And execute the command chmod + x start-all.sh to authorize

Configure multiple environments under the root path before starting the instance

Yum-y install gcc gcc-c++

Start the cluster instance

. / start-all.sh [root@localhost redis] # ps-ef | grep redisroot 14253 10 Oct14? 00:03:27. / redis-server 192.168.5.104 grep redisroot 7001 [cluster] root 14262 10 Oct14? 00:03:38. / redis-server 192.168.5.104 ps 7006 [cluster] root 18571 13962 0 15:37 pts/0 00:00:00 grep redisroot 30364 10 Oct10? 00:15:55. / redis-server 192.168.5.104:7002 [cluster] root 30372 10 Oct10? 00:15:51. / redis-server 192.168.5.104:7003 [cluster] root 30374 10 Oct10? 00:15:31. / redis-server 192.168.5.104:7004 [cluster] root 30379 10 Oct10? 00:15:17. / redis-server 192.168.5.104:7005 [cluster]

Configure the cluster

Cd / app/redis/redis-cluster# creates three master nodes and three slave nodes. Where-replicas1 indicates that there is 1 slave node under each master node, and the slave node can be any number of slaves. . / redis-trib.rb create-- replicas 1 192.168.4.212 Performing hash slots allocation on 7002 192.168.4.212 Performing hash slots allocation on 7002 192.168.4.212 Performing hash slots allocation on 7003 192.168.4.212 192.168.4.212 19004 192.168.4.212 19005 192.168.4.212 Creating cluster > nodes...Using 3 masters:192.168.5.104:7001-master node 192.168.5.104-master node 192.168.5. 104Adding replica 7003-Master node Adding replica 192.168.5.104 Adding replica 192.168.5.104 Adding replica 7006 to 192.168.5.104 Adding replica 7002-Slave node Adding replica 192.168.5.104Adding replica 7004 to 192.168.5.104Adding replica 7004 to 192.168.5.104 Adding replica 7003-slave node > > Trying to optimize slaves allocation for anti-affinity WARNING] Some slaves are in the same host as their masterM: ee942ff5cf8cd0efddcf25b0ff21b5bc1c259589 192.168.5.104 slots:0 7001 slots:0-5460 (5461 slots) master-- hash slot M assigned by the primary node: 3d48e5f1dbb2640d96b4522ece9b8be430bca721 192.168.5.104 ee942ff5cf8cd0efddcf25b0ff21b5bc1c259589 7002 slots:5461-10922 (5462 slots) master-- hash slot M: dfa039f4cb9fed60b44e223a7afa462e34f904f7 192.168.5.10 ee942ff5cf8cd0efddcf25b0ff21b5bc1c259589 7003 slots:10923-16383 (5461 slots) ) master-- hash slot S: 4027313648b8615cec31b2b5c51e25bfc02ade59 192.168.5.104 4027313648b8615cec31b2b5c51e25bfc02ade59 7004 replicates 3d48e5f1dbb2640d96b4522ece9b8be430bca721 assigned by the master node-- Slave node does not have hash slot S: 57331ee1000d4ea652c7eda84b472a38bcd2e21d 192.168.5.104 4027313648b8615cec31b2b5c51e25bfc02ade59 7005 replicates dfa039f4cb9fed60b44e223a7afa462e34f904f7-- Slave node does not have hash slot S: 8ca8eeba19b0acba4fd6f1e9f7be3c4bdb5ea1e5 192.168.5.10 4027313648b8615cec31b2b5c51e25bfc02ade59 slot 7006 replicates ee942ff5cf8cd0efddcf25b0ff21b5bc1c259589-- Slave node does not have hash slot Can I set the above configuration? (type 'yes' to accept): yes-choose yes, which means obeying this master-slave distribution We can also specify slave > > Nodes configuration updated > Assign a different config epoch to each node > > Sending CLUSTER MEET messages to join the clusterWaiting for the cluster to join.... > > Performing Cluster Check (using node 192.168.5.104 additional replica 7001) through the configuration file. The following is the detailed master-slave node distribution M: ee942ff5cf8cd0efddcf25b0ff21b5bc1c259589 192.168.5.104 additional replica 7001 slots:0-5460 (5461 slots) master 1 additional replica (s) S: 4027313648b8615cec31b2b5c51e25bfc02ade59 192.168.5.104: 7004 slots: (0 slots) slave replicates 3d48e5f1dbb2640d96b4522ece9b8be430bca721S: 8ca8eeba19b0acba4fd6f1e9f7be3c4bdb5ea1e5 192.168.5.104 8ca8eeba19b0acba4fd6f1e9f7be3c4bdb5ea1e5 7006 slots: (0 slots) slave replicates ee942ff5cf8cd0efddcf25b0ff21b5bc1c259589M: 3d48e5f1dbb2640d96b4522ece9b8be430bca721 192.168.5.104 master 7002 slots:5461-10922 (5462 slots) master 1 additional replica (s) M: dfa039f4cb9fed60b44e223a7afa462e34f904f7 192.168.5.104 master 7003 slots:10923-16383 (5461 slots) master 1 additional replica (s) S: 57331ee1000d4ea652c7eda84b472a38bcd2e21d 192.168.5.104 slots: (0 slots) slave replicates dfa039f4cb9fed60b44e223a7afa462e34f904f7 OK] All nodes agree about slots configuration. > Check for open slots... > Check slots coverage... [OK] All 16384 slots covered

five。 Cluster testing

Test master-slave high availability

Stop 7001 (master), log in to the slave of 7001, check that the discovery status is master, and use the command info Replication

Cd / app/redis/redis-cluster/7001./redis-cli-c-h 192.168.5.104-p 7001./redis-cli-c-h 192.168.5.104-p 7001 shutdown / / close the 7001 node, if there is no-h parameter, the default connection is 127.0.0.1, if there is no-p parameter, the default connection is port 6379 (all if you use the default There is no-h-p) description:-h+host-p + port number-c is to connect to the cluster, pay attention to the pit, do not add will report an error

When the master master down is back online, the original slave is still master, and the original master has changed from the original master to slave (pro-test)

Test the fragmentation of the cluster

Write 3 pairs of redis in a loop through java code to see if there is data on all 3 master (test all master have data)

The following is the code for java to connect to redis

/ * Cluster mode * * / JedisPoolConfig poolConfig = new JedisPoolConfig (); / / maximum number of connections poolConfig.setMaxTotal (50); / / maximum number of idle poolConfig.setMaxIdle (10) / / maximum allowed waiting time. If no connection is obtained after this time, a JedisException exception will be reported: / / Could not get a resource from the pool poolConfig.setMaxWaitMillis (1000); Set nodes = new LinkedHashSet (); nodes.add (new HostAndPort ("192.168.5.104", Integer.parseInt ("7001")); nodes.add (new HostAndPort ("192.168.5.104", Integer.parseInt ("7002") Nodes.add (new HostAndPort ("192.168.5.104", Integer.parseInt ("7003")); nodes.add (new HostAndPort ("192.168.5.104", Integer.parseInt ("7004"); nodes.add (new HostAndPort ("192.168.5.104", Integer.parseInt ("7005")); nodes.add (new HostAndPort ("192.168.5.104", Integer.parseInt ("7006") @ SuppressWarnings ("resource") JedisCluster cluster = new JedisCluster (nodes, poolConfig); for (int item0)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.