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

The experimental environment uses two servers to simulate six servers (adding network cards) master server Redis1: ens33: 192.168.52.150 ens36: 192.168.52.153 ens37: 192.168.52.154 slave server Redis2: ens33: 192.168.52.148 ens36: 192.168.52.155 ens37: 192.168.52.1561, install Redis on both servers (the operation is the same Demonstrate only one) [root@localhost ~] # yum install gcc gcc-c++ make-y # # installation environment components [root@localhost ~] # mkdir / mnt/tools [root@localhost ~] # mount.cifs / / 192.168.100.100/tools / mnt/tools/ # # mount Password for root@//192.168.100.100/tools: [root@localhost ~] # cd / mnt/tools/redis/ [root@localhost redis] # lsredis-5.0.7 .tar.gz [root@localhost redis] # tar xf redis-5.0.7.tar.gz-C / opt/ # # decompress [root@localhost redis] # cd / opt/ [root@localhost opt] # lsredis-5.0.7 rh [root@localhost opt] # cd redis-5.0.7/ [root@localhost redis-5.0.7] # make # # compile [root@localhost redis-5.0.7] # make PREFIX=/usr/local/redis/ install # # install [root@localhost redis-5.0.7] # cd utils/ [root@localhost utils] #. / install_server.sh # # execute script to configure Welcome to the redis service installerThis script will help you easily set up a running redis serverPlease select the redis port for this instance: [6379] # # default port Selecting default: 6379Please select the redis config file name [/ etc/redis/6379.conf] # # configuration file Selected default-/ etc/redis/ 6379.confPlease select the redis log file name [/ var/log/redis_6379.log] # # Log file Selected default-/ var/log/redis_6379.logPlease select the data directory for this instance [/ var/lib/redis/6379] # # data file Selected default-/ var/lib/redis/6379Please select the redis executable path [] / usr/local/redis/bin/redis-server## executable file path Selected config:Port: 6379Config File: / etc/redis/6379.confLog file: / var/log/redis_6379.logData dir: / var/lib/redis/6379Executable: / usr/local/redis/bin/redis-serverCli Executable: / usr/local/redis/bin/redis-cliIs this ok? Then press ENTER to go on or Ctrl-C to abort.Copied / tmp/6379.conf = > / etc/init.d/redis_6379Installing service...Successfully added to chkconfig successful added to runlevels 345 starting Redis server...Installation successful! [root@localhost utils] # ln-s / usr/local/redis/bin/* / usr/local/bin/ # # it is convenient for the system to identify [root@localhost utils] # netstat-ntap | grep 6379tcp 0 0127.0.0.1 netstat 6379 0.0.0.0VR * LISTEN 44510/redis-server 2, Modify the configuration file on both servers (same operation Only one demo) [root@localhost utils] # vim / etc/redis/6379.conf # bind 127.0.0.1 # # all addresses protected-mode no # # listen on line 70 protected-mode no # # remove line 89 close security port 6379 # # remove line 93, open port 6379daemonize yes # # remove line 137 Start cluster-enabled yes # # with independent process to remove line 833 comments, enable cluster function cluster-config-file nodes-6379.conf # # to remove line 841 comments, cluster name file settings cluster-node-timeout 15000 # # to remove line 847 comments, cluster timeout settings appendonly yes # # to remove line 700 comments Enable aof persistence [root@localhost utils] # / etc/init.d/redis_6379 restart # # restart service Stopping... Redis stoppedStarting Redis server... [root@localhost utils] # cd / var/lib/redis/6379/ [root@localhost 6379] # lsappendonly.aof dump.rdb nodes-6379.conf # # generate aof,rdb and node files 3, install rvm on the master server Ruby control cluster software (master server only) [root@localhost utils] # gpg-- keyserver hkp://keys.gnupg.net-- recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3## import key file gpg: created directory'/ root/.gnupg'gpg: new configuration file'/ root/.gnupg/gpg.conf' created gpg: warning: options in'/ root/.gnupg/gpg.conf' are not used gpg during this run : key ring'/ root/.gnupg/secring.gpg' established gpg: key ring'/ root/.gnupg/pubring.gpg' established gpg: download key 'D39DC0E3' Trust database established from hkp server keys.gnupg.netgpg: / root/.gnupg/trustdb.gpg: gpg: key D39DC0E3: public key "Michal Papis (RVM signing)" imported gpg: no absolute trust keys found gpg: total number of processed: 1gpg: imported: 1 (RSA: 1) [root@localhost utils] # curl-sSL https://get.rvm.io | bash -s stable # # installation rvm....// omission process [root@localhost utils] # source / etc/profile.d/rvm.sh # # execution environment variable [root@localhost utils] # rvm list known # # list the versions that ruby can install [root@localhost utils] # rvm install 2.4.1 # # install version 2.4.1 [root@localhost utils] # rvm use 2.4.1 # # use the rubyruby2.4.1 version Using / usr/local/rvm/gems/ruby-2.4.1 [root@localhost utils] # ruby- v # # to view the current ruby2.4.1 version ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux] [root@localhost utils] # gem install redis # install RedisFetching redis-4.1.3.gemSuccessfully installed redis-4.1.3Parsing documentation for again Redis-4.1.3Installing ri documentation for redis-4.1.3Done installing documentation for redis after 1 seconds1 gem installed [root@localhost utils] # 4 、 Add two network cards to the primary server

[root@localhost utils] # service network restart # # restart the network card [root@localhost utils] # systemctl stop firewalld.service # # turn off the firewall [root@localhost utils] # setenforce 0 [root@localhost utils] # ifconfig ens33: flags=4163 mtu 1500 inet 192.168.52.150 netmask 255.255.255.0 broadcast 192.168.52.255 inet6 fe80::5134:22f5:842b:5201 prefixlen 64 scopeid 0x20 ether 00:0c:29:0d:f1 75 txqueuelen 1000 (Ethernet) RX packets 91575 bytes 119014065 (113.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 28442 bytes 2443621 (2.3MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0ens36: flags=4163 mtu 1500 inet 192.168.52.153 netmask 255.255.255.0 broadcast 192.168.52.255 inet6 fe80::84f1:53d8:a97a:d450 prefixlen 64 scopeid 0x20 ether 00: 0c:29:0d:f1:89 txqueuelen 1000 (Ethernet) RX packets 128 bytes 18873 (18.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 42 bytes 6253 (KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0ens37: flags=4163 mtu 1500 inet 192.168.52.154 netmask 255.255.255.0 broadcast 192.168.52.255 inet6 fe80::74f5:2344:c59b:4fdb prefixlen 64 scopeid 0x20 ether 00:0c:29:0d:f1:7f txqueuelen 1000 (Ethernet) RX packets 107bytes 16849 (16.4KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 29 bytes 4601 (4.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 05, Add two network cards to the slave server as well

[root@slave utils] # service network restart # # restart the network card [root@slave utils] # systemctl stop firewalld.service # # turn off the firewall [root@slave utils] # setenforce 0 [root@localhost utils] # ifconfig ens33: flags=4163 mtu 1500 inet 192.168.52.148 netmask 255.255.255.0 broadcast 192.168.52.255 inet6 fe80::c776:9d00:618:88f2 prefixlen 64 scopeid 0x20 ether 00:0c:29:37:e9:25 txqueuelen 1000 (Ethernet) RX packets 65481 bytes 86357533 (82.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 21069 bytes 1892475 (1.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0ens36: flags=4163 mtu 1500 inet 192.168.52.155 netmask 255.255.255.0 broadcast 192.168.52.255 inet6 fe80::d3e5:cd6b:26f8:fd1f prefixlen 64 scopeid 0x20 ether 00:0c:29 : 37:e9:39 txqueuelen 1000 (Ethernet) RX packets 143bytes 17342 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 38 bytes 5940 (5.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0ens37: flags=4163 mtu 1500 inet 192.168.52.156 netmask 255.255.255.0 broadcast 192.168.52.255 inet6 fe80::222b:77ad:8da2:4ea6 prefixlen 64 scopeid 0x20 Ether 00:0c:29:37:e9:2f txqueuelen 1000 (Ethernet) RX packets 114bytes 14481 (14.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 30 bytes 4661 (4.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 06, Create a cluster on the master server # # 6 instances are divided into three groups Each group of one master and one slave [root@localhost utils] # redis-cli-- cluster create 192.168.52.150 cluster create 6379 192.168.52.153 cluster create 6379 192.168.52.154buret 6379 192.168.52.148cluster create 6379 192.168.52.155Ze6379 192.168.52.156 cluster-replicas # create a cluster Each group has one master and one slave > > Performing hash slots allocation on 6 nodes...Master [0]-> Slots 0-5460Master [1]-> Slots 5461-10922Master [2]-> Slots 10923-16383Adding replica 192.168.52.155 Slots 6379 to 192.168.52.150:6379Adding replica 192.168.52.156Slots 6379 to 192.168.52.153:6379Adding replica 192.168.52.148 to 6379 to 192.168.52.154 to 6379M: b9dfae79d92141a7bad172a344e0696f356a875f 192.168.52.150 Slots: [0-16383] (5461 slots) master # # 128 129135 Master M: b9dfae79d92141a7bad172a344e0696f356a875f 192.168.52.153 slots 6379 slots: [0-16383] (5462 slots) masterM: b9dfae79d92141a7bad172a344e0696f356a875f 192.168.52.154masterM 6379 slots: [0-16383] (5461 slots) masterS: ebc69ee01cf293b3af9930cac2dba03b4475336b 192.168.52.148lv 6379 replicates b9dfae79d92141a7bad172a344e0696f356a875f # # 136137138 is a copy of S: ebc69ee01cf293b3af9930cac2dba03b4475336b 192.168.52.15515 masterM 6379 replicates b9dfae79d92141a7bad172a344e0696f356a875fS: ebc69ee01cf293b3af9930cac2dba03b4475336b 192.168.52.156pur6379 replicates b9dfae79d92141a7bad172a344e0696f356a875f...Can I set the above configuration? (type 'yes' to accept): yes # # Select yes > 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.52.150 slots 6379) M: b9dfae79d92141a7bad172a344e0696f356a875f 192.168.52.150 slots 6379 slots: [0-16383] (16384 slots) master 1 additional replica (s) S: ebc69ee01cf293b3af9930cac2dba03b4475336b 192.168.52.155 RV 6379 slots: (0 slots) slave replicates b9dfae79d92141a7bad172a344e0696f356a875f [OK] All nodes agree about Slots configuration. > > Check for open slots... > Check slots coverage... [OK] All 16384 slots covered. [root@localhost utils] # 7, Verify the principle of cluster reading and writing [root@localhost utils] # redis-cli-h 192.168.52.150-p 6379 # # Master server 192.168.52.150 OK 6379 > set name zhangsan # # creation key pair OK 192.168.52.150 keys * 1) "name" 192.168.52.150 keys 6379 > get name "zhangsan" 192.168.52.150 set name zhangsan 6379 > exit [root@localhost utils] # redis-cli-h 192.168.52.148-p 6379 # # check from server 192.168.52.148zhangsan > keys * # there are also 1) "name" 192.168.52.148zhangsan > exit [root@localhost utils] #

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.