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

This article focuses on "how to deploy Redis 4.0 cluster environment", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to deploy a Redis 4.0 cluster environment.

Experimental environment:

Redis version: 4.0.9

Three OS:redhat 6.4s

IP:10.10.1.129 Hostname:wjq1 Port: [7001/7002/7003]

IP:10.10.1.130 Hostname:wjq2 Port: [7004/7005/7006]

IP:10.10.1.131 Hostname:wjq3 Port: [7007/7008/7009]

First, install redis

For more information about the installation of redis 4.0, please see: CentOS 7.4.Installation of redis 4.0detailed steps [http://blog.itpub.net/31015730/viewspace-2155307/]

Download, extract, compile, and install redis4.0.9

For detailed installation process, please refer to:

[root@wjq1 wjq-software] # tar-zxvf redis-4.0.9.tar.gz

[root@wjq1 redis-4.0.9] # make

Cd src & & make all

Make [1]: Entering directory `/ usr/local/redis/redis-4.0.9/src'

CC adlist.o

In file included from adlist.c:34:

Zmalloc.h:50:31: error: jemalloc/jemalloc.h: No such file or directory

Zmalloc.h:55:2: error: # error "Newer version of jemalloc required"

Make [1]: * * [adlist.o] Error 1

Make [1]: Leaving directory `/ usr/local/redis/redis-4.0.9/src'

Make: * * [all] Error 2

There is a passage in README.md:

Explain:

Redis in the installation of the memory allocator allocator, if there is an environment variable MALLOC, it will be used to create the Redis environment variable. If not, the default allocator is used; after the redis2.4 version, jemalloc is used for memory management by default, because jemalloc has been shown to solve fragmentation problem (memory fragmentation problem) better than libc, and libc is not the default allocator, but if you don't have jemalloc and only libc, of course make goes wrong. So add such a parameter.

Solution:

[root@wjq1 src] # make MALLOC=libc

If you want to use jemalloc, install jemalloc; if you use yum installation, you need to configure the EPEL source.

[root@wjq1 src] # make MALLOC=libc

[root@wjq1 redis-4.0.9] # make PREFIX=/usr/local/redis install

[root@wjq1 redis] # ll

Total 8

Drwxr-xr-x 2 root root 4096 Jun 5 11:32 bin

Drwxr-xr-x 6 root root 4096 Jun 5 11:24 redis-4.0.9

[root@wjq1 redis-4.0.9] # cp redis.conf / etc/redis/

Create a redis node

1. First create a directory / etc/redis/redis_cluster on the 10.10.1.129 host

[root@wjq1 ~] # mkdir / etc/redis/redis_cluster

2. Under the redis_cluster directory, create directories named 7000, 7001, and 7002, and copy redis.conf to these three directories

[root@wjq1 ~] # mkdir / etc/redis/redis_cluster/ {7001, 7002, 7003}

[root@wjq1 ~] # cp / etc/redis/redis.conf / etc/redis/redis_cluster/7001

[root@wjq1 ~] # cp / etc/redis/redis.conf / etc/redis/redis_cluster/7002

[root@wjq1 ~] # cp / etc/redis/redis.conf / etc/redis/redis_cluster/7003

3. Modify these three configuration files respectively, and the modified contents are as follows:

[root@wjq1 ~] # cat / etc/redis/redis_cluster/7001/redis.conf | grep-v ^ # | grep-v ^ $

/ / the default ip is 127.0.0.1, which needs to be changed to an ip accessible by other node machines, otherwise the corresponding port cannot be accessed when the cluster is created and the cluster cannot be created.

Bind 10.10.1.129

/ / Port 7000pr 7002pr 7003

Port 7001

/ / redis runs in the background

Daemonize yes

/ / pidfile files correspond to 70001.7002

Pidfile / var/run/redis/redis_7001.pid

/ / logfile files correspond to 70001.7002

Logfile / var/log/redis/redis_7001.log

/ / rdb files correspond to 70001.7002

Dbfilename dump7001.rdb

/ / Open the cluster and remove the comment #

Cluster-enabled yes

/ / configuration of the cluster. For the first time, the configuration file starts the automatic generation of 7000pr 7001pr 7002.

Cluster-config-file nodes-7001.conf

/ / request timeout. Default is 15 seconds, which can be set by yourself.

Cluster-node-timeout 15000

For more information about the parameters in the redis configuration file, please see: detailed explanation of the parameters in the redis configuration file [http://blog.itpub.net/31015730/viewspace-2154818/]

Then repeat the above three steps on the other two machines (10.10.1.130,10.10.1.131), just change the directory to 7003, 7004, 7005, 7006, 7007, 7008 and modify the corresponding configuration files according to this rule.

3. Start the redis of each node

Node one:

[root@wjq1] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7001/redis.conf

[root@wjq1] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7002/redis.conf

[root@wjq1] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7003/redis.conf

[root@wjq1 ~] #

[root@wjq1 ~] # ps-ef | grep redis

Root 40414 10 12:36? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.129:7001 [cluster]

Root 40419 10 12:36? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.129:7002 [cluster]

Root 40424 10 12:36? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.129:7003 [cluster]

Root 40429 38753 0 12:36 pts/0 00:00:00 grep redis

[root@wjq1 ~] #

[root@wjq1 ~] # netstat-tuplan | grep redis

Tcp 00 10.10.1.129 17003 0.0.0.0 VR * LISTEN 40424/redis-server

Tcp 00 10.10.1.129 7001 0.0.0.0 LISTEN 40414/redis-server

Tcp 00 10.10.1.129 7002 0.0.0.0 LISTEN 40419/redis-server

Tcp 00 10.10.1.129 7003 0.0.0.0 LISTEN 40424/redis-server

Tcp 00 10.10.1.129 17001 0.0.0.0 LISTEN 40414/redis-server

Tcp 00 10.10.1.129 17002 0.0.0.0 LISTEN 40419/redis-server

Node 2:

[root@wjq2] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7004/redis.conf

[root@wjq2] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7005/redis.conf

[root@wjq2] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7006/redis.conf

[root@wjq2 ~] #

[root@wjq2 ~] # ps-ef | grep redis

Root 39261 10 12:38? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.130:7004 [cluster]

Root 39266 10 12:38? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.130:7005 [cluster]

Root 39271 10 12:38? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.130:7006 [cluster]

Root 39276 38355 0 12:38 pts/0 00:00:00 grep redis

[root@wjq2 ~] #

[root@wjq2 ~] # netstat-tuplan | grep redis

Tcp 00 10.10.1.130 17004 0.0.0.0 VR * LISTEN 39261/redis-server

Tcp 00 10.10.1.130 17005 0.0.0.0 *

Tcp 00 10.10.1.130 17006 0.0.0.0 VR * LISTEN 39271/redis-server

Tcp 00 10.10.1.130 7004 0.0.0.0 VR * LISTEN 39261/redis-server

Tcp 00 10.10.1.130 7005 0.0.0.0 *

Tcp 00 10.10.1.130 7006 0.0.0.0 VR * LISTEN 39271/redis-server

Node 3:

[root@wjq3] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7007/redis.conf

[root@wjq3] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7008/redis.conf

[root@wjq3] # / usr/local/redis/bin/redis-server / etc/redis/redis_cluster/7009/redis.conf

[root@wjq3 ~] #

[root@wjq3 ~] # ps-ef | grep redis

Root 24742 10 13:00? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.131:7007 [cluster]

Root 24758 10 13:01? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.131:7008 [cluster]

Root 24763 1 1 13:01? 00:00:00 / usr/local/redis/bin/redis-server 10.10.1.131:7009 [cluster]

Root 24768 23890 1 13:01 pts/0 00:00:00 grep redis

[root@wjq3 ~] #

[root@wjq3 ~] # netstat-tuplan | grep redis

Tcp 00 10.10.1.131 17007 0.0.0.0 * LISTEN 24742/redis-server

Tcp 00 10.10.1.131 17008 0.0.0.0 * LISTEN 24758/redis-server

Tcp 00 10.10.1.131 17009 0.0.0.0 * LISTEN 24763/redis-server

Tcp 00 10.10.1.131 7007 0.0.0.0 * LISTEN 24742/redis-server

Tcp 00 10.10.1.131 7008 0.0.0.0 * LISTEN 24758/redis-server

Tcp 00 10.10.1.131 7009 0.0.0.0 * LISTEN 24763/redis-server

Note: make sure that each node is configured correctly and can be started successfully

Find a random node to test:

[root@wjq1] # / usr/local/redis/bin/redis-cli-h 10.10.1.129-p 7002

10.10.1.129VR 7002 >

10.10.1.129VR 7002 > keys *

(empty list or set)

10.10.1.129VR 7002 >

10.10.1.129VR 7002 > set name wjq

(error) CLUSTERDOWN Hash slot not served

The connection was successful, but it seems to have been misreported.

(error) CLUSTERDOWN Hash slot not served (no hash slots for clusters), what the heck is this?

This is because although we have configured and started the Redis cluster service, they are not in a cluster yet, cannot find each other directly, and have no storage location, which is called slot (slot).

4. Create a cluster by redis-trib

After all the instances of Redis are running, you also need the redis-trib.rb tool to create the cluster. The redis-trib.rb binaries are located in the src directory under the home directory of the Redis package. Running the tool depends on the Ruby environment and gem, so you need to install it in advance.

1. Install ruby [you can install any node]

[root@wjq1 ~] # yum install ruby

[root@wjq1] # ruby-v

Ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

[root@wjq1 ~] #

[root@wjq1] # gem-v

-bash: gem: command not found

After installing ruby using yum, there is no gem command and the version of ruby 1.8.7 does not meet the subsequent requirements. The latest redis requires ruby version above 2.2, and most of the systems come with ruby lower than 2.2. Enter the following command to delete the old version:

[root@wjq1 ~] # yum remove ruby

Here are the completed steps to install ruby2.4:

(1) download ruby2.4 or higher version first

Download address: https://www.ruby-lang.org/en/downloads/

(2) before installing ruby, install openssl first, otherwise many problems will be encountered in the subsequent process of installing ruby. The detailed errors will be solved at the end of the article.

OpenSSL official website: https://www.openssl.org/

Download the OpenSSL version 1.0.2n source code:

[root@wjq1~] # wget https://www.openssl.org/source/openssl-1.0.2n.tar.gz

Extract and enter the openssl code root directory:

[root@wjq1 ~] # tar zxvf openssl-1.0.2n.tar.gz

[root@wjq1 ~] # cd openssl-1.0.2n

Configure, compile, install:

[root@wjq1 openssl-1.0.2n] #. / config

[root@wjq1 openssl-1.0.2n] # make

[root@wjq1 openssl-1.0.2n] # make install

After the installation is complete, the default installation location is / usr/local/ssl

(3) decompress, compile and install ruby

[root@wjq2] # mkdir-p / usr/local/ruby2.4

[root@wjq2 ~] # cd / wjq-software/

[root@wjq2 wjq-software] # ll

Total 120240

Drwxr-xr-x 20 root root 4096 Jun 5 15:57 openssl-1.0.2n

-rw-r--r-- 1 root root 5375802 Jun 5 15:51 openssl-1.0.2n.tar.gz

-rw-r--r-- 1 root root 91648 Jun 5 15:50 redis-4.0.1.gem

-rw-r--r-- 1 root root 14225338 Jun 5 15:53 ruby-2.4.4.tar.gz

[root@wjq2 wjq-software] #

[root@wjq2 wjq-software] # tar-zxvf ruby-2.4.4.tar.gz

[root@wjq2 ruby-2.4.4] # / configure-prefix=/usr/local/ruby2.4-- with-openssl-include=/usr/local/ssl/include/-- with-openssl-lib=/usr/local/ssl/lib

[root@wjq2 ruby-2.4.4] # make

[root@wjq2 ruby-2.4.4] # make install

[root@wjq2 ruby-2.4.4] # / usr/local/ruby2.4/bin/ruby-v

Ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux]

[root@wjq2 ruby-2.4.4] #

[root@wjq2 ruby-2.4.4] # / usr/local/ruby2.4/bin/gem-v

2.6.14.1

[root@wjq2 ruby-2.4.4] # vim ~ / .bash_profile

RUBY_PATH=/usr/local/ruby2.4/bin

PATH=$PATH:$HOME/bin:/usr/local/mongdb/bin:$RUBY_PATH

2. Use gem to install redis and install redis.

[root@wjq2 ~] # gem install redis

# # if the download may fail due to the source, download it manually and install it

Download address: https://rubygems.org/gems/redis/versions/

[root@wjq2 ~] # gem install / wjq-software/redis-4.0.1.gem

Successfully installed redis-4.0.1

Parsing documentation for redis-4.0.1

Installing ri documentation for redis-4.0.1

Done installing documentation for redis after 0 seconds

WARNING: Unable to pull data from 'https://rubygems.org/': timed out (https://api.rubygems.org/specs.4.8.gz)

1 gem installed

3. Start to create a cluster. This is the real cluster.

Redis officially provides redis-trib.rb, which is located in the src directory of the unzipped directory.

Explain this command briefly: call the ruby command to create the cluster:

-- replicas 1 means that the master-slave replication ratio is 1:1, that is, one master node corresponds to one slave node. Then, by default, each master node and the corresponding slave node services, as well as the size of the solt, are assigned to us by default, because there are only 16383 solt in the Redis cluster. Of course, you can specify that the nodes can be redistributed later.

[root@wjq2] # / usr/local/redis/redis-4.0.9/src/redis-trib.rb create-- replicas 1\

> 10.10.1.129VR 7001 10.10.1.129VR 7002 10.10.1.129VR 7003\

> 10.10.1.130 VR 7004 10.10.1.130 VR 7005 10.10.1.130 VR 7006\

> 10.10.1.131VR 7007 10.10.1.131VR 7008 10.10.1.131VR 7009

> Creating cluster

> Performing hash slots allocation on 9 nodes...

Using 4 masters:

10.10.1.129:7001

10.10.1.130:7004

10.10.1.131:7007

10.10.1.129:7002

Adding replica 10.10.1.131:7008 to 10.10.1.129:7001

Adding replica 10.10.1.129:7003 to 10.10.1.130:7004

Adding replica 10.10.1.130:7006 to 10.10.1.131:7007

Adding replica 10.10.1.131:7009 to 10.10.1.129:7002

Adding replica 10.10.1.130:7005 to 10.10.1.129:7001

M: 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957 10.10.1.129:7001

Slots:0-4095 (4096 slots) master

M: 924d61969343b5cc2200bd3a2277e815dc76048c 10.10.1.129:7002

Slots:12288-16383 (4096 slots) master

S: b9ba251f575b5396da4bea307e25a98d85b3c504 10.10.1.129:7003

Replicates a4a5de0be9bb5704eec17cbe0223076eb38fc4a4

M: a4a5de0be9bb5704eec17cbe0223076eb38fc4a4 10.10.1.130:7004

Slots:4096-8191 (4096 slots) master

S: bdc2f6b254459a6a6d038d93e5a3d3a67fe3e936 10.10.1.130:7005

Replicates 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957

S: 4ae20400d02e57e274f9b9f29d4ba120aa2b574c 10.10.1.130:7006

Replicates 2b0f974e151cd798f474107ac68a47e188cc88a2

M: 2b0f974e151cd798f474107ac68a47e188cc88a2 10.10.1.131:7007

Slots:8192-12287 (4096 slots) master

S: b240d86fdf6abc73df059baf64b930387664da15 10.10.1.131:7008

Replicates 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957

S: 5b7989d5370aef41679e92a6bd34c30ac3be3581 10.10.1.131:7009

Replicates 924d61969343b5cc2200bd3a2277e815dc76048c

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.10.1.129 7001)

M: 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957 10.10.1.129:7001

Slots:0-4095 (4096 slots) master

2 additional replica (s)

S: 4ae20400d02e57e274f9b9f29d4ba120aa2b574c 10.10.1.130:7006

Slots: (0 slots) slave

Replicates 2b0f974e151cd798f474107ac68a47e188cc88a2

M: 924d61969343b5cc2200bd3a2277e815dc76048c 10.10.1.129:7002

Slots:12288-16383 (4096 slots) master

1 additional replica (s)

M: 2b0f974e151cd798f474107ac68a47e188cc88a2 10.10.1.131:7007

Slots:8192-12287 (4096 slots) master

1 additional replica (s)

S: 5b7989d5370aef41679e92a6bd34c30ac3be3581 10.10.1.131:7009

Slots: (0 slots) slave

Replicates 924d61969343b5cc2200bd3a2277e815dc76048c

S: b9ba251f575b5396da4bea307e25a98d85b3c504 10.10.1.129:7003

Slots: (0 slots) slave

Replicates a4a5de0be9bb5704eec17cbe0223076eb38fc4a4

S: b240d86fdf6abc73df059baf64b930387664da15 10.10.1.131:7008

Slots: (0 slots) slave

Replicates 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957

S: bdc2f6b254459a6a6d038d93e5a3d3a67fe3e936 10.10.1.130:7005

Slots: (0 slots) slave

Replicates 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957

M: a4a5de0be9bb5704eec17cbe0223076eb38fc4a4 10.10.1.130:7004

Slots:4096-8191 (4096 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.

The above output indicates that the cluster has been built successfully!

Description:

M: 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957 primary node id

S: b240d86fdf6abc73df059baf64b930387664da15 is the id of the slave node

At present, 7001, 7002, 7004, 7007 master nodes, 7003, 7005, 7008, 7009 are slave nodes, and confirm to you whether you agree to this configuration. After entering yes, the cluster creation will begin.

5. Cluster verification

1. Log in to a node at will and view the information of the cluster and the node

Add the parameter-C to connect to the cluster, because redis.conf changes bind to ip address, so the-h parameter cannot be omitted, and the-p parameter is the port number.

[root@wjq2] # / usr/local/redis/bin/redis-cli-h 10.10.1.130-p 7005-c

10.10.1.130,7005 >

10.10.1.130V 7005 > cluster info

Cluster_state:ok # Cluster status

Cluster_slots_assigned:16384 # number of slots allocated

Cluster_slots_ok:16384 # correctly allocated slots

Cluster_slots_pfail:0

Cluster_slots_fail:0

Cluster_known_nodes:9 # number of cluster nodes

Cluster_size:4

Cluster_current_epoch:9

Cluster_my_epoch:1

Cluster_stats_messages_ping_sent:215

Cluster_stats_messages_pong_sent:225

Cluster_stats_messages_meet_sent:5

Cluster_stats_messages_sent:445

Cluster_stats_messages_ping_received:222

Cluster_stats_messages_pong_received:220

Cluster_stats_messages_meet_received:3

Cluster_stats_messages_received:445

10.10.1.130,7005 >

10.10.1.130V 7005 > cluster nodes

4ae20400d02e57e274f9b9f29d4ba120aa2b574c 10.10.1.130 connected 7006 "17006 slave 2b0f974e151cd798f474107ac68a47e188cc88a2 0 1528186867658 7

924d61969343b5cc2200bd3a2277e815dc76048c 10.10.1.129 connected 7002 17002 master-01528186865000 2 connected 12288-16383

B240d86fdf6abc73df059baf64b930387664da15 10.10.1.131 connected 7008 slave 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957 01528186865643 8 connected

7a047cfaae70c30d0d7e1a5d9854eb7f11afe957 10.10.1.129 connected 7001mm 17001 master-01528186862612 1 connected 0-4095

Bdc2f6b254459a6a6d038d93e5a3d3a67fe3e936 10.10.1.130 connected 7005mm 17005 myself,slave 7a047cfaae70c30d0d7e1a5d9854eb7f11afe957 0 1528186863000 5

B9ba251f575b5396da4bea307e25a98d85b3c504 10.10.1.129 connected 7003 connected 17003 slave a4a5de0be9bb5704eec17cbe0223076eb38fc4a4 0 1528186865000 4

A4a5de0be9bb5704eec17cbe0223076eb38fc4a4 10.10.1.130 connected 7004 17004 master-01528186866650 4 connected 4096-8191

5b7989d5370aef41679e92a6bd34c30ac3be3581 10.10.1.131 connected 7009 slave 924d61969343b5cc2200bd3a2277e815dc76048c 01528186866000 9 connected

2b0f974e151cd798f474107ac68a47e188cc88a2 10.10.1.131 connected 7007 17007 master-01528186864631 7 connected 8192-12287

10.10.1.130,7005 >

2. Insert a key in one of the nodes

10.10.1.130VR 7005 > keys *

(empty list or set)

10.10.1.130,7005 >

10.10.1.130V 7005 > set name wjq

-> Redirected to slot [5798] located at 10.10.1.130 purl 7004

OK

10.10.1.130VR 7004 > get name

"wjq"

Verify success on other nodes

[root@wjq3] # / usr/local/redis/bin/redis-cli-h 10.10.1.131-p 7009-c

10.10.1.131VR 7009 > get name

-> Redirected to slot [5798] located at 10.10.1.130 purl 7004

"wjq"

10.10.1.130PUR 7004 >

VI. Summary

When redis cluster is designed, it takes into account decentralization and middleware, that is to say, each node in the cluster is equal and peer-to-peer, and each node saves its own data and the state of the whole cluster. Each node is connected to all other nodes, and these connections remain active, which ensures that we only need to connect to any node in the cluster to get the data of other nodes.

Instead of using traditional consistent hashes to allocate data, Redis clusters allocate data in another way called hash slot. Redis cluster allocates 16384 slot by default. When we set a key, we use the CRC16 algorithm to get the slot we belong to, and then divide the key to the nodes in the hash slot. The specific algorithm is: CRC16 (key)% 16384. So when we saw set and get during the test, we jumped directly to the node on port 7000.

The Redis cluster stores the data in a master node and then synchronizes the data between the master and its corresponding salve. When the data is read, the data is also obtained from the corresponding master node according to the consistent hashing algorithm. Only when a master is dead will a corresponding salve node be started to act as a master.

It should be noted that there must be 3 or more master nodes, otherwise the creation of the cluster will fail, and when the number of surviving master nodes is less than half of the total number of nodes, the entire cluster will not be able to provide services.

However, there are some problems encountered in the process of building. Here are the ways to deal with the problems:

Summary of the problems encountered in the construction process:

[root@wjq1 ~] # gem install redis

# if the download may fail due to the source, download it manually and install it

[root@wjq2 ~] # gem install / wjq-software/redis-4.0.1.gem

ERROR: While executing gem... (Gem::Exception)

Unable to require openssl, install OpenSSL and rebuild ruby (preferred) or use non-HTTPS sources

Reason:

Openssl is missing and the openssl package needs to be installed, but I already installed an openssl-1.0.2n.tar.gz before

Solution:

[root@wjq1 ruby-2.4.4] # cd. / ext/openssl/

[root@wjq1 openssl] # ruby extconf.rb

Checking for t_open () in-lnsl... No

Checking for socket () in-lsocket... No

Checking for openssl/ssl.h... No

Prompt that ssl.h was not found because of an error: openssl/ssl.h: do not have that file, then follow the following method

[root@wjq1 openssl] # ruby extconf.rb-with-openssl-include=/usr/local/ssl/include/-with-openssl-lib=/usr/local/ssl/lib

Checking for t_open () in-lnsl... No

Checking for socket () in-lsocket... No

Checking for openssl/ssl.h... Yes

Checking for OpenSSL version is 0.9.8 or later... Yes

.

Checking for SSL_CTX_set_min_proto_version in openssl/ssl.h... No

Checking for SSL_CTX_get_security_level (). No

Checking for X509_get0_notBefore (). No

Checking for SSL_SESSION_get_protocol_version (). No

Creating extconf.h

Creating Makefile

Next, soft link the include directory under the ruby source directory to the / directory:

[root@wjq1 openssl] # ln-s / wjq-software/ruby-2.4.4/include/ /

[root@wjq1 openssl] # ll /

Lrwxrwxrwx 1 root root 33 Jun 5 15:08 include-> / wjq-software/ruby-2.4.4/include/

Then execute make, and if you configure openssl without the-fPIC parameter, the following error will occur

[root@wjq1 openssl] # make

Compiling openssl_missing.c

Compiling ossl.c

Compiling ossl_asn1.c

.

Compiling ossl_x509revoked.c

Compiling ossl_x509store.c

Linking shared-object openssl.so

/ usr/bin/ld: / usr/local/ssl/lib/libssl.a (s3_meth.o): relocation R_X86_64_32 against `.rodata 'can not be used when making a shared object; recompile with-fPIC

/ usr/local/ssl/lib/libssl.a: could not read symbols: Bad value

Collect2: ld returned 1 exit status

Make: * * [openssl.so] Error 1

Prompt to retry compiling openssl with the-fPIC parameter. So recompile openssl. When this error occurs, you need to recompile openssl, add the-fPIC parameter when compiling, and then execute it again.

[root@wjq1 openssl] # make

Compiling openssl_missing.c

Compiling ossl.c

Compiling ossl_asn1.c

.

Compiling ossl_x509store.c

Linking shared-object openssl.so

[root@wjq1 openssl] # make install

/ usr/bin/install-c-m 0755 openssl.so / usr/local/lib/ruby/site_ruby/2.4.0/x86_64-linux

Installing default openssl libraries

After the installation is successful, in retrospect, we have solved the various problems encountered in configuring the cluster, and use gem install to install the ruby redis interface again:

[root@wjq1 ~] # gem install / wjq-software/redis-4.0.1.gem

Successfully installed redis-4.0.1

Parsing documentation for redis-4.0.1

Installing ri documentation for redis-4.0.1

Done installing documentation for redis after 0 seconds

WARNING: Unable to pull data from 'https://rubygems.org/': timed out (https://api.rubygems.org/specs.4.8.gz)

1 gem installed

At this point, I believe you have a deeper understanding of "how to deploy Redis 4.0 cluster environment". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.