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

Editor to share with you how to build a redis cluster under windows, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's learn about it!

Foreword:

Clustering refers to adding the number of servers to provide the same services, such as weapons to achieve a stable and efficient state. Why use redis clusters? Redis clusters can enhance the read and write ability of redis.

Let's formally learn about redis clusters.

Preparatory work:

Four components are required: Redis, Ruby language runtime environment, Ruby-driven redis-xxxx.gem for Redis, and redis-trib.rb, a tool for creating Redis clusters. Use the redis-trib.rb tool to create a Redis cluster, and since the file is written in Ruby, you need to install the Ruby development environment and drive redis-xxxx.gem.

1) download the Redis installation file: https://github.com/MSOpenTech/redis/releases/ Magi Redis provides download files in msi and zip formats, and download zip format Redis-x64-3.2.100 here.

2) download the Ruby installation file: http://dl.bintray.com/oneclick/rubyinstaller/rubyinstaller-2.2.4-x64.exe

3) download the driver of Redis in Ruby environment: https://rubygems.org/gems/redis/versions/3.2.2. For compatibility, version 3.2.2 is downloaded here.

Note: download in the related links in the lower right corner of the page

4) download the ruby script file redis-trib.rb provided officially by Redis to create a Redis cluster, and the path is as follows: https://raw.githubusercontent.com/MSOpenTech/redis/3.0/src/redis-trib.rb

Install Redis

Decompress the downloaded Redis-x64-3.2.100.zip. For ease of use, it is recommended to put it in the root directory of the drive letter, such as D:\ Redis-Cluster\ Redis-x64-3.2.100.

Install Redis and run 3 instances (Redis cluster requires at least 3 nodes, less than 3 cannot be created)

Six different Redis instances are started through the configuration file, and since the default port of Redis is 6379, 6380, 6381, 6382, 6383, 6384, 6385 are used to run six Redis instances.

Note:

(1) to avoid unnecessary errors, save the configuration file in utf8 format as much as possible, and do not contain comments

(2) the following two ways to save logs in the configuration file (save in file and save to System Log), please select one of them according to your needs:

The recording level of the loglevel notice # log. Notice is the logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6380_log.txt" # suitable for the production environment. Specify the retention path of the log. By default, it is created under the Redis installation directory. If there are subdirectories that need to be created manually, whether the Logs directory syslog-enabled yes # uses the Syslog syslog-ident redis6380 # ID in the Syslog.

The method of saving in a file is used here, so first create a new Logs folder under the Redis directory D:\ Redis-Cluster\ Redis-x64-3.2.100.

Under the root directory of the Redis installation, create a configuration file with the encoding format utf-8: redis.6380.conf, redis.6381.conf, redis.6382.conf, redis.6383.conf, redis.6384.conf, redis.6385.conf.

Redis.6380.conf 、

Port 6380 loglevel notice logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6380_log.txt" appendonly yesappendfilename "appendonly.6380.aof" cluster-enabled yes cluster-config-file nodes.6380.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

Redis.6381.conf 、

Port 6381 loglevel notice logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6381_log.txt" appendonly yesappendfilename "appendonly.6381.aof" cluster-enabled yes cluster-config-file nodes.6381.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

Redis.6382.conf 、

Port 6382 loglevel notice logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6382_log.txt" appendonly yesappendfilename "appendonly.6382.aof" cluster-enabled yes cluster-config-file nodes.6382.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

Redis.6383.conf 、

Port 6383 loglevel notice logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6383_log.txt" appendonly yesappendfilename "appendonly.6383.aof" cluster-enabled yes cluster-config-file nodes.6383.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

Redis.6384.conf 、

Port 6384 loglevel notice logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6384_log.txt" appendonly yesappendfilename "appendonly.6384.aof" cluster-enabled yes cluster-config-file nodes.6384.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

Redis.6385.conf

Port 6385 loglevel notice logfile "D:/Redis-Cluster/Redis-x64-3.2.100/Logs/redis6385_log.txt" appendonly yesappendfilename "appendonly.6385.aof" cluster-enabled yes cluster-config-file nodes.6385.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

The configuration is explained as follows:

The recording level of port 6380 # port number loglevel notice # log. Notice is the logfile "Logs/redis6380_log.txt" # suitable for production environment. Specify the retention path of log. By default, it is created under the Redis installation directory. If there are any subdirectories, you need to create them manually. Whether the Logs directory syslog-enabled yes # at this location uses Syslog syslog-ident redis6380 # in the identification name of Syslog appendonly yes # whether the data is saved in aof format appendfilename "appendonly.6380.aof" # data save file cluster-enabled yes # is opened Cluster cluster-config-file nodes.6380.confcluster-node-timeout 15000cluster-slave-validity-factor 10cluster-migration-barrier 1cluster-require-full-coverage yes

Save the above configuration files to the Redis directory and install six redis services using these configuration files, with the following command:

D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-install D:/Redis-Cluster/Redis-x64-3.2.100/redis.6380.conf-service-name redis6380D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-install D:/Redis-Cluster/Redis-x64-3.2.100/redis.6381.conf-service-name redis6381D:/Redis-Cluster/Redis-x64-3 . 2.100/redis-server.exe-service-install D:/Redis-Cluster/Redis-x64-3.2.100/redis.6382.conf-service-name redis6382D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-install D:/Redis-Cluster/Redis-x64-3.2.100/redis.6383.conf-service-name redis6383D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-- Service-install D:/Redis-Cluster/Redis-x64-3.2.100/redis.6384.conf-service-name redis6384D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-install D:/Redis-Cluster/Redis-x64-3.2.100/redis.6385.conf-service-name redis6385

Note:

1) configuration files such as redis.6380.conf should use the full path to avoid problems in restarting the Redis cluster.

2) the uninstall command is:

D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-uninstall D:/Redis-Cluster/Redis-x64-3.2.100/redis.6380.conf-service-name redis6380D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-uninstall D:/Redis-Cluster/Redis-x64-3.2.100/redis.6381.conf-service-name redis6381D:/Redis-Cluster/Redis-x64-3 . 2.100/redis-server.exe-service-uninstall D:/Redis-Cluster/Redis-x64-3.2.100/redis.6382.conf-service-name redis6382D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-uninstall D:/Redis-Cluster/Redis-x64-3.2.100/redis.6383.conf-service-name redis6383D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-- Service-uninstall D:/Redis-Cluster/Redis-x64-3.2.100/redis.6384.conf-service-name redis6384D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-uninstall D:/Redis-Cluster/Redis-x64-3.2.100/redis.6385.conf-service-name redis6385

Start the six services with the following command:

D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-start-service-name redis6380D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-start-- service-name redis6381D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-- service-start-- service-name redis6382D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-- Service-start-service-name redis6383D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-start-service-name redis6384D:/Redis-Cluster/Redis-x64-3.2.100/redis-server.exe-service-start-service-name redis6385

Execution result:

Install ruby

(1) installation in Ruby environment.

Double-click the downloaded "rubyinstaller-2.2.4-x64.exe" to install it. Similarly, for ease of operation, it is also recommended to install it in the root directory of the drive letter, such as C:\ Ruby22-x64. Select the last two options here during installation.

It means to add ruby to the environment variable of the system, and the command of ruby can be used directly in the cmd command.

(1) install the driver of Redis in Ruby environment

Copy the downloaded "Redis driver file (redis-3.2.2.gem) in Ruby environment" to the root directory of the Ruby installation (C:\ Ruby22-x64).

Then execute the installation command as follows:

Gem install-local path_to_gem/filename.gem

Create a Redis cluster

Copy the downloaded ruby script file redis-trib.rb for creating a Redis cluster to the root directory of the Redis installation (D:\ Redis-Cluster\ Redis-x64-3.2.100).

(1) use redis-trib.rb to create a Redis cluster

Change to the Redis directory under MD (D:\ Redis-Cluster\ Redis-x64-3.2.100)

D:/Redis-Cluster/Redis-x64-3.2.100/redis-trib.rb create-- replicas 1 127.0.0.1 replicas 6380 127.0.1

D:\ Redis-Cluster\ Redis-x64-3.2.100 > redis-trib.rb create-- replicas 1 127.0.0.1 Creating clusterConnecting to node 6380 127.0.0.1redis-trib.rb create: OKConnecting to node 127.0.0.1: OKConnecting to node 127.0.1: To node 127.0.0.1 to node 6383: OKConnecting to node 127.0.0.1 Performing hash slots allocation on 6385: OK > Performing hash slots allocation on 6 nodes...Using 3 Performing hash slots allocation on 127.0.1 to 127.0.0.1:6380Adding replica to 127.0.0.1:6380Adding replica 127.0.1 .0.0.1: 6385 to 127.0.0.1 slots:0 6382M: bb6ef615bb0ae13275943caec0db9d30b9f35c5e 127.0.0.1 slots:0 6380 slots:0-5460 (5461 slots) masterM: b4d120f2983ad683f7b68992e1ba414722238db7 127.0.0.1 masterM 6381 slots:5461-10922 (5462 slots) masterM: 837779b3965e2c9d4dd4385750aaaaf9a9039fb0 127.0.1 slots:10923-16383 (5461 slots) masterS: 5d154137180284d926ef51a91fc75f9438249ef8 127.0.0.1 slots:0 6383 replicates bb6ef615bb0ae13275943caec0db9d30b9f35c5eS: ad151680a3e36cf2083ef822be0bdb075a7d36de 127.0.1 slots:10923 6384 replicates b4d120f2983ad683f7b68992e1ba414722238db7S: 9a2260a5a6a2add84b622a453a6a7b86a29d180d. 0.0.1:6385 replicates 837779b3965e2c9d4dd4385750aaaaf9a9039fb0Can 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 clusterWaiting for the cluster to join... > > Performing Cluster Check (using node 127.0.0.1 slots 6380) M: bb6ef615bb0ae13275943caec0db9d30b9f35c5e 127.0.1 slots 6380 slots:0-5460 (5461 slots) masterM: b4d120f2983ad683f7b68992e1ba414722238db7 127.0.1 purl 6381 slots:5461-10922 (5462 slots) masterM: 837779b3965e2c9d4dd4385750aaaaf9a9039fb0 127.0.0.1 (5461 slots) masterM: 5d154137180284d926ef51a91fc75f9438249ef8 127.0.0.1 slots 6383 slots: (0 slots) master replicates bb6ef615bb0ae13275943caec0db9d30b9f35c5eM: ad151680a3e36cf2083ef822be0bdb075a7d36de 127.0.0.1 slots 6384 slots: (0 slots) master replicates b4d120f2983ad683f7b68992e1ba414722238db7M: 9a2260a5a6a2add84b622a453a6a7b86a29d180d 127.0.0.1 slots: (0 slots) master replicates 837779b3965e2c9d4dd4385750aaaaf9a9039fb0 [OK] All nodes agree about slots configuration. > > Check for open slots... > > Check slots coverage... [OK] All 16384 slots covered.

Note:

(1)-- replicas # specifies that each master node in the cluster is equipped with several slave nodes, which is set to 1 here.

(2) the use of redis-trib.rb tools

, create: create cluster, check: check cluster, info: view cluster information, fix: repair cluster, reshard: online migration slot, rebalance: balance the number of cluster nodes slot, add-node: add new nodes to the cluster, del-node: remove nodes from the cluster, set-timeout: set heartbeat connection timeout between cluster nodes, call: execute commands on all nodes in the cluster, import: import external redis data into the cluster

(2) verify whether the creation is really successful.

Enter the following command:

Redis-trib.rb check 127.0.0.1:6380

If the actual information is as follows, it means that the Redis cluster created is fine.

D:\ Redis-Cluster\ Redis-x64-3.2.100 > redis-trib.rb check 127.0.0.1:6380Connecting to node 127.0.0.1 redis-trib.rb check 127.0.0.1:6380Connecting to node 6380: OKConnecting to node 127.0.0.1 redis-trib.rb check 127.0.0.1:6380Connecting to node 6383: OKConnecting to node 127.0.0.1 redis-trib.rb check 127.0.0.1:6380Connecting to node 6382: OKConnecting to node 127.0.0.1 using node 6384: OKConnecting to node 127.0.16381: OK > > Performing Cluster Check (using node 127.0.0. 1additional replica 6380) M: bb6ef615bb0ae13275943caec0db9d30b9f35c5e 127.0.0.1 master 6380 slots:0-5460 (5461 slots) master 1 additional replica (s) S: 5d154137180284d926ef51a91fc75f9438249ef8 127.0.0.1 master 6383 slots: (0 slots) slave replicates bb6ef615bb0ae13275943caec0db9d30b9f35c5eM: 837779b3965e2c9d4dd4385750aaaaf9a9039fb0 127.0.0.1 slots:10923-16383 master 1 additional replica (s) S: ad151680a3e36cf2083ef822be0bdb075a7d36de 127.0.0.1 slots: (0 Slots) slave replicates b4d120f2983ad683f7b68992e1ba414722238db7S: 9a2260a5a6a2add84b622a453a6a7b86a29d180d 127.0.0.1 slots 6385 slots: (0 slots) slave replicates 837779b3965e2c9d4dd4385750aaaaf9a9039fb0M: b4d120f2983ad683f7b68992e1ba414722238db7 127.0.0.1 additional replica 6381 slots:5461-10922 (5462 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.D:\ Redis-Cluster\ Redis-x64-3.2.100 >

(3) Information query

Use Redis client Redis-cli.exe to view the number of data records and cluster-related information

These are all the contents of this article entitled "how to build redis clusters under windows". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.