Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "Redis cluster deployment method". Many people will encounter such a dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Redis and ruby are installed on the master and slave nodes.

[root@D2-LZY245 redis-4.0.1] # yum-y install ruby ruby-devel rubygems rpm-build

[root@D2-LZY245 redis-4.0.1] # gem install redis

2. The master node creates the cluster directory, configures the parameters, and starts

[root@D2-LZY245 ~] # cd redis-4.0.1/

[root@D2-LZY245 redis-4.0.1] # mkdir redis_cluster

[root@D2-LZY245 redis-4.0.1] # cd redis_cluster/

[root@D2-LZY245 redis_cluster] # mkdir 7000 7001 7002

[root@D2-LZY245 redis_cluster] # cp.. / redis.conf 7000/

[root@D2-LZY245 redis_cluster] # vim 7000/redis.conf

[root@D2-LZY245 redis_cluster] # egrep'^ port | ^ bind | ^ daemonize | ^ pidfile | ^ cluster-enabled | ^ cluster-config-file | ^ cluster-node-timeout | ^ appendonly' 7000/redis_7000.conf

Bind 10.163.89.245

Port 7000

Daemonize yes

Pidfile / var/run/redis_7000.pid

Appendonly yes

Cluster-enabled yes

Cluster-config-file nodes-7000.conf

Cluster-node-timeout 15000

[root@D2-LZY245 redis_cluster] # mv 7000/redis.conf 7000/redis_7000.conf

[root@D2-LZY245 redis_cluster] # cp 7000/redis_7000.conf 7001/redis_7001.conf

[root@D2-LZY245 redis_cluster] # cp 7000/redis_7000.conf 7002/redis_7002.conf

[root@D2-LZY245 redis_cluster] # vim 7001/redis_7001.conf

[root@D2-LZY245 redis_cluster] # egrep'^ port | ^ bind | ^ daemonize | ^ pidfile | ^ cluster-enabled | ^ cluster-config-file | ^ cluster-node-timeout | ^ appendonly' 7001/redis_7001.conf

Bind 10.163.89.245

Port 7001

Daemonize yes

Pidfile / var/run/redis_7001.pid

Appendonly yes

Cluster-enabled yes

Cluster-config-file nodes-7001.conf

Cluster-node-timeout 15000

[root@D2-LZY245 redis_cluster] # vim 7002/redis_7002.conf

[root@D2-LZY245 redis_cluster] # egrep'^ port | ^ bind | ^ daemonize | ^ pidfile | ^ cluster-enabled | ^ cluster-config-file | ^ cluster-node-timeout | ^ appendonly' 7002/redis_7002.conf

Bind 10.163.89.245

Port 7002

Daemonize yes

Pidfile / var/run/redis_7002.pid

Appendonly yes

Cluster-enabled yes

Cluster-config-file nodes-7002.conf

Cluster-node-timeout 15000

[root@D2-LZY245 redis_cluster] # cd..

[root@D2-LZY245 redis-4.0.1] # src/redis-server redis_cluster/7000/redis_7000.conf

[root@D2-LZY245 redis-4.0.1] # src/redis-server redis_cluster/7001/redis_7001.conf

[root@D2-LZY245 redis-4.0.1] # src/redis-server redis_cluster/7002/redis_7002.conf

[root@D2-LZY245 redis-4.0.1] # netstat-tunlp | grep 700

Tcp 00 10.163.89.245 17000 0.0.0.0 * LISTEN 28447/src/redis-ser

Tcp 00 10.163.89.245 17001 0.0.0.0 * LISTEN 28423/src/redis-ser

Tcp 00 10.163.89.245 17002 0.0.0.0 * LISTEN 28432/src/redis-ser

Tcp 00 10.163.89.245 7000 0.0.0.0 * LISTEN 28447/src/redis-ser

Tcp 00 10.163.89.245 7001 0.0.0.0 * LISTEN 28423/src/redis-ser

Tcp 00 10.163.89.245 7002 0.0.0.0 * LISTEN 28432/src/redis-ser

3. Create the cluster directory from the node, configure the parameters, and start

[root@D2-TRAIN15 ~] # cd redis-4.0.1

[root@D2-TRAIN15 redis-4.0.1] # mkdir redis_cluster

[root@D2-TRAIN15 redis-4.0.1] # cd redis_cluster/

[root@D2-TRAIN15 redis_cluster] # mkdir 7003 7004 7005

[root@D2-TRAIN15 redis_cluster] # cp.. / redis.conf 7003/

[root@D2-TRAIN15 redis_cluster] # vim 7003/redis.conf

[root@D2-TRAIN15 redis_cluster] # egrep'^ port | ^ bind | ^ daemonize | ^ pidfile | ^ cluster-enabled | ^ cluster-config-file | ^ cluster-node-timeout | ^ appendonly' 7003/redis.conf

Bind 10.163.89.15

Port 7003

Daemonize yes

Pidfile / var/run/redis_7003.pid

Appendonly yes

Cluster-enabled yes

Cluster-config-file nodes-7003.conf

Cluster-node-timeout 15000

[root@D2-TRAIN15 redis_cluster] # mv 7003/redis.conf 7003/redis_7003.conf

[root@D2-TRAIN15 redis_cluster] # cp 7003/redis_7003.conf 7004/redis_7004.conf

[root@D2-TRAIN15 redis_cluster] # cp 7003/redis_7003.conf 7005/redis_7005.conf

[root@D2-TRAIN15 redis_cluster] # vim 7004/redis_7004.conf

[root@D2-TRAIN15 redis_cluster] # egrep'^ port | ^ bind | ^ daemonize | ^ pidfile | ^ cluster-enabled | ^ cluster-config-file | ^ cluster-node-timeout | ^ appendonly' 7004/redis_7004.conf

Bind 10.163.89.15

Port 7004

Daemonize yes

Pidfile / var/run/redis_7004.pid

Appendonly yes

Cluster-enabled yes

Cluster-config-file nodes-7004.conf

Cluster-node-timeout 15000

[root@D2-TRAIN15 redis_cluster] # vim 7005/redis_7005.conf

[root@D2-TRAIN15 redis_cluster] # egrep'^ port | ^ bind | ^ daemonize | ^ pidfile | ^ cluster-enabled | ^ cluster-config-file | ^ cluster-node-timeout | ^ appendonly' 7005/redis_7005.conf

Bind 10.163.89.15

Port 7005

Daemonize yes

Pidfile / var/run/redis_7005.pid

Appendonly yes

Cluster-enabled yes

Cluster-config-file nodes-7005.conf

Cluster-node-timeout 15000

[root@D2-TRAIN15 redis_cluster] # cd..

[root@D2-TRAIN15 redis-4.0.1] # src/redis-server redis_cluster/7003/redis_7003.conf

[root@D2-TRAIN15 redis-4.0.1] # src/redis-server redis_cluster/7004/redis_7004.conf

[root@D2-TRAIN15 redis-4.0.1] # src/redis-server redis_cluster/7005/redis_7005.conf

[root@D2-TRAIN15 redis-4.0.1] # netstat-tunlp | grep 700

Tcp 00 10.163.89.15 17003 0.0.0.0 * LISTEN 14258/src/redis-ser

Tcp 00 10.163.89.15 17004 0.0.0.0 * LISTEN 14263/src/redis-ser

Tcp 00 10.163.89.15 17005 0.0.0.0 * LISTEN 14268/src/redis-ser

Tcp 00 10.163.89.15 7003 0.0.0.0 * LISTEN 14258/src/redis-ser

Tcp 00 10.163.89.15 7004 0.0.0.0 * LISTEN 14263/src/redis-ser

Tcp 00 10.163.89.15 7005 0.0.0.0 * LISTEN 14268/src/redis-ser

[root@D2-TRAIN15 redis-4.0.1] #

4. Create a cluster

[root@D2-LZY245 redis-4.0.1] # src/redis-trib.rb create-- replicas 1 10.163.89.245Vl7000 10.163.89.245VOL7001 10.163.89.245VOL7002 10.163.89.15VOL7003 10.163.89.15VOLFOR 7004 10.163.89.15VOL7005

> Creating cluster

> Performing hash slots allocation on 6 nodes...

Using 3 masters:

10.163.89.245:7000

10.163.89.15:7003

10.163.89.245:7001

Adding replica 10.163.89.15:7004 to 10.163.89.245:7000

Adding replica 10.163.89.245:7002 to 10.163.89.15:7003

Adding replica 10.163.89.15:7005 to 10.163.89.245:7001

M: b545390b3e8c3602e13978cf28f6ef7dd76b6197 10.163.89.245:7000

Slots:0-5460 (5461 slots) master

M: 0e26e28f3c531357db73e522bb6279350ff5275e 10.163.89.245:7001

Slots:10923-16383 (5461 slots) master

S: 8164d21461a9a5612e9657863c1c214f8c116a8e 10.163.89.245:7002

Replicates e81c2072be94bdf7729b10088a312ff519cb0f2b

M: e81c2072be94bdf7729b10088a312ff519cb0f2b 10.163.89.15:7003

Slots:5461-10922 (5462 slots) master

S: 4284f88f612157caa6611173d347ec4ec9f9554b 10.163.89.15:7004

Replicates b545390b3e8c3602e13978cf28f6ef7dd76b6197

S: d141fe7c975728b1243d6d314914179a7febb306 10.163.89.15:7005

Replicates 0e26e28f3c531357db73e522bb6279350ff5275e

Can I set the above configuration? (type 'yes' to accept): 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 10.163.89.245v7000)

M: b545390b3e8c3602e13978cf28f6ef7dd76b6197 10.163.89.245:7000

Slots:0-5460 (5461 slots) master

1 additional replica (s)

S: 8164d21461a9a5612e9657863c1c214f8c116a8e 10.163.89.245:7002

Slots: (0 slots) slave

Replicates e81c2072be94bdf7729b10088a312ff519cb0f2b

S: d141fe7c975728b1243d6d314914179a7febb306 10.163.89.15:7005

Slots: (0 slots) slave

Replicates 0e26e28f3c531357db73e522bb6279350ff5275e

S: 4284f88f612157caa6611173d347ec4ec9f9554b 10.163.89.15:7004

Slots: (0 slots) slave

Replicates b545390b3e8c3602e13978cf28f6ef7dd76b6197

M: e81c2072be94bdf7729b10088a312ff519cb0f2b 10.163.89.15:7003

Slots:5461-10922 (5462 slots) master

1 additional replica (s)

M: 0e26e28f3c531357db73e522bb6279350ff5275e 10.163.89.245:7001

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.

5. Test

Set key on port 7000 of the primary node:

[root@D2-LZY245 ~] # cd redis-4.0.1/

[root@D2-LZY245 redis-4.0.1] # src/redis-cli-h 10.163.89.245-c-p 7000

10.163.89.245VR 7000 > set key1 "hello world"

-> Redirected to slot [9189] located at 10.163.89.15 purl 7003

OK

10.163.89.15 virtual 7003 > keys *

1) "key1"

At the slave node port 7005:

[root@D2-TRAIN15 redis-4.0.1] # src/redis-cli-h 10.163.89.15-c-p 7005

10.163.89.15VOL7005 > get key1

-> Redirected to slot [9189] located at 10.163.89.15 purl 7003

"hello world"

This is the end of the content of "Redis Cluster deployment method". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.