I'm going to take you all to the end CentOS 7 Install in Redis 6.x course . I'm learning Redis Cluster The cluster before , We need to build a cluster environment first . The machines are limited , The goal is to build... On a machine 6 Nodes , Form a three master and three slave cluster model .
You can go directly to Redis Download the latest stability pack from the official website , Address ：https://redis.io/download. Or use command ：sudo wget http://download.redis.io/releases/redis-6.0.9.tar.gz Download installation package ..
/opt/soft Under the table of contents , And create a directory mkdir redisCluster Used to place the cluster configuration file . stay redisCluster Execute under directory mkdir 7000 7001 7002 7003 7004 7005 establish 6 Each directory corresponds to each node redis.conf The configuration template .tar -zxf redis-6.0.9.tar.gz -C redisCluster Unzip to redisCluster Directory .Before we compile, we need to confirm that gcc edition , since redis 6.0.0 after , compile redis Need to support C11 characteristic ,C11 Characteristic in 4.9 Introduced in .Centos 7 Default gcc Version is 4.8.5, So we need to upgrade gcc edition .
Compile error
Otherwise, the following error log will be encountered during compilation ：
In file included from server.c:31:0:
server.c:4999:59: error: ‘struct redisServer’ has no member named ‘cluster’
(server.cluster_enabled && nodeIsMaster(server.cluster->myself)));
^
cluster.h:58:27: note: in definition of macro ‘nodeIsMaster’
#define nodeIsMaster(n) ((n)->flags & CLUSTER_NODE_MASTER)
^
server.c: In function ‘main’:
server.c:5047:11: error: ‘struct redisServer’ has no member named ‘sentinel_mode’
server.sentinel_mode = checkForSentinelMode(argc,argv);
^
server.c:5064:15: error: ‘struct redisServer’ has no member named ‘sentinel_mode’
if (server.sentinel_mode) {
^
server.c:5131:19: error: ‘struct redisServer’ has no member named ‘sentinel_mode’
if (server.sentinel_mode && configfile && *configfile == '-') {
^
server.c:5153:168: error: ‘struct redisServer’ has no member named ‘sentinel_mode’
serverLog(LL_WARNING, "Warning: no config file specified, using the default config. In order to specify a config file use %s /path/to/%s.conf", argv[0], server.sentinel_mode ? "sentinel" : "redis");
^
server.c:5158:11: error: ‘struct redisServer’ has no member named ‘supervised’
server.supervised = redisIsSupervised(server.supervised_mode);
^
server.c:5158:49: error: ‘struct redisServer’ has no member named ‘supervised_mode’
server.supervised = redisIsSupervised(server.supervised_mode);
^
server.c:5159:28: error: ‘struct redisServer’ has no member named ‘daemonize’
int background = server.daemonize && !server.supervised;
^
server.c:5159:49: error: ‘struct redisServer’ has no member named ‘supervised’
int background = server.daemonize && !server.supervised;
^
server.c:5163:29: error: ‘struct redisServer’ has no member named ‘pidfile’
if (background || server.pidfile) createPidFile();
^
server.c:5168:16: error: ‘struct redisServer’ has no member named ‘sentinel_mode’
if (!server.sentinel_mode) {
^
server.c:5178:19: error: ‘struct redisServer’ has no member named ‘cluster_enabled’
if (server.cluster_enabled) {
^
server.c:5186:19: error: ‘struct redisServer’ has no member named ‘ipfd_count’
if (server.ipfd_count > 0 || server.tlsfd_count > 0)
^
server.c:5186:44: error: ‘struct redisServer’ has no member named ‘tlsfd_count’
if (server.ipfd_count > 0 || server.tlsfd_count > 0)
^
server.c:5188:19: error: ‘struct redisServer’ has no member named ‘sofd’
if (server.sofd > 0)
^
server.c:5189:94: error: ‘struct redisServer’ has no member named ‘unixsocket’
serverLog(LL_NOTICE,"The server is now ready to accept connections at %s", server.unixsocket);
^
server.c:5190:19: error: ‘struct redisServer’ has no member named ‘supervised_mode’
if (server.supervised_mode == SUPERVISED_SYSTEMD) {
^
server.c:5191:24: error: ‘struct redisServer’ has no member named ‘masterhost’
if (!server.masterhost) {
^
server.c:5201:19: error: ‘struct redisServer’ has no member named ‘supervised_mode’
if (server.supervised_mode == SUPERVISED_SYSTEMD) {
^
server.c:5208:15: error: ‘struct redisServer’ has no member named ‘maxmemory’
if (server.maxmemory > 0 && server.maxmemory < 1024*1024) {
^
server.c:5208:39: error: ‘struct redisServer’ has no member named ‘maxmemory’
if (server.maxmemory > 0 && server.maxmemory < 1024*1024) {
^
server.c:5209:176: error: ‘struct redisServer’ has no member named ‘maxmemory’
serverLog(LL_WARNING,"WARNING: You specified a maxmemory value that is less than 1MB (current value is %llu bytes). Are you sure this is what you really want?", server.maxmemory);
^
server.c:5212:31: error: ‘struct redisServer’ has no member named ‘server_cpulist’
redisSetCpuAffinity(server.server_cpulist);
^
server.c: In function ‘hasActiveChildProcess’:
server.c:1480:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
server.c: In function ‘allPersistenceDisabled’:
server.c:1486:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
server.c: In function ‘writeCommandsDeniedByDiskError’:
server.c:3826:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
server.c: In function ‘iAmMaster’:
server.c:5000:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
....
Solution
yum -y install gcc gcc-c++ make tcl yum -y install centos-release-scl yum -y install devtoolset-9-gcc devtoolset-9-gcc-c++ devtoolset-9-binutils scl enable devtoolset-9 bash
It can be solved after upgrading make Report the wrong question .
Be careful ：scl Command activation is only temporary , sign out xshell Or the restart will return to the original gcc edition . If it's going to take effect in the long run , The implementation is as follows sudo echo "source /opt/rh/devtoolset-9/enable" >>/etc/profile.
cd /opt/soft/redisCluster/redis-6.0.9 Switch to directory execution make .
Compile complete use make install Yes redis Installation , command ：sudo make install.
cd /opt/soft/redisCluster/redis-6.0.9 take redis.conf Copy them to 7000 7001 7002 7003 7004 Directory .
Revision respectively 6 individual redis.conf
## 7000-7005 port port 7000 ## Background start daemonize yes ## If you are in a stand-alone simulation cluster, you must specify bind Of IP, If not modified ip If you use the program to connect to the cluster, you will report an error bind 192.168.221.150 ## Turn on redis-cluster colony cluster-enabled yes ## Each instance also contains the path to the file that stores the configuration of this node , By default nodes.conf, Automatically create cluster-config-file nodes_7000.conf ## Overtime cluster-node-timeout 500 ## Turn on aof appendonly yes # notes cluster Replication is not allowed in a cluster . #replicaof 127.0.0.1 9000 # Turn off protection mode , If you need to set a password to open , More complicated , According to their own needs to protected-mode no
Each profile just needs to be modified port and cluster-config-file That's all right. .
Start node
Get into redisCluster Catalog , Execute the command to start each node in turn .redis-6.0.9/src/redis-server 700x/redis.conf Note that each node profile is specified , If you do not specify a configuration file, it will be used by default src Configuration below .
Create clusters
Go to any node , Execute the following command to create a cluster
The instructions are as follows ：
redis-6.0.9/src/redis-cli --cluster create 172.16.90.152:7000 172.16.90.152:7001 172.16.90.152:7002 172.16.90.152:7003 172.16.90.152:7004 172.16.90.152:7005 --cluster-replicas 1
Cluster parameter interpretation ：
Console response ：
>>> Performing hash slots allocation on 6 nodes... Master[0] -> Slots 0 - 5460 Master[1] -> Slots 5461 - 10922 Master[2] -> Slots 10923 - 16383 Adding replica 172.16.90.152:7004 to 172.16.90.152:7000 Adding replica 172.16.90.152:7005 to 172.16.90.152:7001 Adding replica 172.16.90.152:7003 to 172.16.90.152:7002 >>> Trying to optimize slaves allocation for anti-affinity [WARNING] Some slaves are in the same host as their master M: 06c56f5a6a4436108fae931be499465985141d39 172.16.90.152:7000 slots:[0-5460] (5461 slots) master M: 0ab7c9efd97319d94a8ea52452ec58f7708d812d 172.16.90.152:7001 slots:[5461-10922] (5462 slots) master M: 096f076d99363270c02785a2fb298e2ee65d3f07 172.16.90.152:7002 slots:[10923-16383] (5461 slots) master S: 69d621060295eb433af3e34e702142df0fd4d73d 172.16.90.152:7003 replicates 06c56f5a6a4436108fae931be499465985141d39 S: 1d37df0aa0e2310aedb5a380f95cc818256003f8 172.16.90.152:7004 replicates 0ab7c9efd97319d94a8ea52452ec58f7708d812d S: d9204f6da875a4b2522c5fa25d9e6c1f95cf51ea 172.16.90.152:7005 replicates 096f076d99363270c02785a2fb298e2ee65d3f07 Can I set the above configuration? (type 'yes' to accept):
Can I set the above configuration? (type 'yes' to accept): Ask if you want to confirm the node slots Distribution plan , We type in ‘yes’.
>>> Nodes configuration updated >>> Assign a different config epoch to each node >>> Sending CLUSTER MEET messages to join the cluster Waiting for the cluster to join . >>> Performing Cluster Check (using node 172.16.90.152:7000) M: 06c56f5a6a4436108fae931be499465985141d39 172.16.90.152:7000 slots:[0-5460] (5461 slots) master 1 additional replica(s) S: 1d37df0aa0e2310aedb5a380f95cc818256003f8 172.16.90.152:7004 slots: (0 slots) slave replicates 0ab7c9efd97319d94a8ea52452ec58f7708d812d M: 0ab7c9efd97319d94a8ea52452ec58f7708d812d 172.16.90.152:7001 slots:[5461-10922] (5462 slots) master 1 additional replica(s) S: d9204f6da875a4b2522c5fa25d9e6c1f95cf51ea 172.16.90.152:7005 slots: (0 slots) slave replicates 096f076d99363270c02785a2fb298e2ee65d3f07 S: 69d621060295eb433af3e34e702142df0fd4d73d 172.16.90.152:7003 slots: (0 slots) slave replicates 06c56f5a6a4436108fae931be499465985141d39 M: 096f076d99363270c02785a2fb298e2ee65d3f07 172.16.90.152:7002 slots:[10923-16383] (5461 slots) master 1 additional replica(s) [OK] All nodes agree about slots configuration. >>> Check for open slots... >>> Check slots coverage... [OK] All 16384 slots covered.
[OK] All 16384 slots covered.
That's it ！
redis-6.0.9/src/redis-cli --cluster check 172.16.90.152:7000
When using redis-6.0.9/src/redis-cli --cluster create 172.16.90.152:7000 172.16.90.152:7001 172.16.90.152:7002 172.16.90.152:7003 172.16.90.152:7004 172.16.90.152:7005 --cluster-replicas 1 After creating the cluster , Create... At once , Permanent use . After that, start each node directly to build the cluster .
Closing order ：redis-6.0.9/src/redis-cli -c -h 192.168.124.23 -p 7004 shutdown
Enter the cluster command redis-cli -c -h host -p prot No -c The parameter does not enter the cluster
After building the cluster , Looking forward to the next 「Redis High availability ：Cluster How much data can be supported ？」
This article is from WeChat official account. - Code byte （MageByte）
The source and reprint of the original text are detailed in the text , If there is any infringement , Please contact the yunjia_community@tencent.com Delete .
Original publication time ： 2021-04-05
Participation of this paper Tencent cloud media sharing plan , You are welcome to join us , share .