安裝單機版redis

寫文章時最新版本為：redis-4.0.1.tar.gz

可以先下載到windows作業系統，然後拷貝到centos。

下載成功後，在centos上建立一個目錄，存放我們的軟體，我比較喜歡放在/soft目錄下。

[[email protected] /]# mkdir /soft

然後利用WinScp工具拷貝到centos系統，放在/soft/目錄下。

可以在 這兒下載http://download.csdn.net/download/u013308504/10250657   解壓後可以直接使用   可以省略步驟3和4

1、安裝gcc

[[email protected] ~]# yum install gcc

中間有2次提示，要求輸入：yes 或 y，我們按照提示來就可以。

2、安裝pstree

[[email protected] ~]# yum install psmisc

中間有1次提示，要求輸入：y。按照提示來就可以。

3、解壓tar包

[[email protected] /]# cd /soft

[[email protected] soft]# tar zxvf redis-4.0.1.tar.gz

[[email protected] soft]# mv redis-4.0.1 /usr/local/redis

4、編譯安裝

[[email protected] soft]# cd /usr/local/redis

[[email protected] redis]# make MALLOC=libc

[[email protected] redis]# make & make install

說明：如果在make的時候不指定記憶體管理方式，會報錯的：

zmalloc.h:50:31: 致命錯誤：jemalloc/jemalloc.h：沒有那個檔案或目錄。

malloc是管理記憶體碎片的。

5、啟動reids 看是否安裝成功

[[email protected] redis]# ./src/redis-server redis.conf

如果報沒得許可權 在當前目錄下 執行命令 chmod 777 ./src/redis-server

如果成功，如下圖：

然後新開終端，開啟redis客戶端

[[email protected] ~]# cd /usr/local/redis/

[[email protected] redis]# src/redis-cli

表示已經啟動成功。

我相信單機安裝有點linux基礎的同學都能安裝成功。

叢集redis

1、安裝ruby

清理已安裝過的 ruby

yum erase ruby ruby-libs ruby-mode ruby-rdoc ruby-irb ruby-ri ruby-docs

手動下載 

https://cache.ruby-lang.org/pub/ruby/2.2/ruby-2.2.7.tar.gz

上傳到linux環境 並解壓

tar xf ruby-2.2.7.tar.gz

剛開始用命令yum install ruby安裝，但是是2.0以下的版本。我把它解除安裝了，重新下的2.0以上的包安裝

把安裝包上傳到指定目錄，並解壓

命令：tar zxvf ruby-2.2.7.tar.gz；解壓後，進入ruby-2.2.7目錄下，依次執行下面命令

命令：./configure

命令：make & make install

新增環境變數 export PATH=/usr/local/ruby-2.2.7/bin:$PATH

2、檢視ruby資訊

命令：ruby -v

3、要支援redis的通訊，需要下載redis相關包

命令：gem install redis

新建6個資料夾 cp -RF redis 7001 cp -RF redis 7002....

redis.conf

配置檔案 全部替換即可redis.conf 並修改相應的IP 與埠

#自己的ip
bind 192.168.33.159
port 7001
timeout 0
tcp-keepalive 0
loglevel notice
databases 16
save 900 1
save 300 10
save 60 10000
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename dump.rdb
dir ./
################################# REPLICATION #################################
slave-serve-stale-data yes
slave-read-only yes
repl-diskless-sync no
repl-diskless-sync-delay 5
repl-disable-tcp-nodelay no
slave-priority 100
############################## APPEND ONLY MODE ###############################
appendonly yes
appendfilename "appendonly.7001.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
aof-load-truncated yes
lua-time-limit 5000
cluster-enabled yes
cluster-config-file nodes-7001.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes
################################# SLOW LOG ###################################
slowlog-log-slower-than 10000
slowlog-max-len 128
latency-monitor-threshold 0
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-size -2
list-compress-depth 0
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
hll-sparse-max-bytes 3000
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10

aof-rewrite-incremental-fsync yes

啟動叢集 前 先啟動所有的單個redis

[[email protected] 7001]# ./src/redis-trib.rb create --replicas 1 192.168.33.159:7001 192.168.33.159:7002 192.168.33.159:7003 192.168.33.159:7004 192.168.33.159:7005 192.168.33.159:7006
>>> Creating cluster

[ERR] Sorry, can't connect to node 192.168.33.159:7001

出現這個錯誤 是由於redis.conf 配置檔案是127.0.0.1 修改成對應的內網IP即可

[[email protected] src]# ./redis-trib.rb create --replicas 1 192.168.33.159:7001 192.168.33.159:7002 192.168.33.159:7003 192.168.33.159:7004 192.168.33.159:7005 192.168.33.159:7006

-bash: ./redis-trib.rb: 許可權不夠

[[email protected] src]# chmod  777 ./redis-trib.r

使用redis-trib.rb 啟動 叢集

[[email protected] 7001]# ./src/redis-trib.rb create --replicas 1 192.168.33.159:7001 192.168.33.159:7002 192.168.33.159:7003 192.168.33.159:7004 192.168.33.159:7005 192.168.33.159:7006

-------------啟動日誌

>>> Creating cluster
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
192.168.33.159:7001
192.168.33.159:7002
192.168.33.159:7003
Adding replica 192.168.33.159:7005 to 192.168.33.159:7001
Adding replica 192.168.33.159:7006 to 192.168.33.159:7002
Adding replica 192.168.33.159:7004 to 192.168.33.159:7003
>>> Trying to optimize slaves allocation for anti-affinity
[WARNING] Some slaves are in the same host as their master
M: f4becd9fda2f030d45894adf29299b713464deca 192.168.33.159:7001
   slots:0-5460 (5461 slots) master
M: 1761b5c929704f4b28577e8a45118265af3000ec 192.168.33.159:7002
   slots:5461-10922 (5462 slots) master
M: 2fb1ad83a7663a54eb873e99f69a02a678ec5fe1 192.168.33.159:7003
   slots:10923-16383 (5461 slots) master
S: 8e822227ee657be7e781cfb9ad3057b0a20fe89f 192.168.33.159:7004
   replicates f4becd9fda2f030d45894adf29299b713464deca
S: fadce9dbd7c96990116c712d7e120a293427358a 192.168.33.159:7005
   replicates 1761b5c929704f4b28577e8a45118265af3000ec
S: 0efa39d0ec0d487c8ed2b019ce977fc9b8c933fb 192.168.33.159:7006
   replicates 2fb1ad83a7663a54eb873e99f69a02a678ec5fe1
Can I set the above configuration? (type 'yes' to accept): yes ---輸入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 192.168.33.159:7001)
M: f4becd9fda2f030d45894adf29299b713464deca 192.168.33.159:7001
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: fadce9dbd7c96990116c712d7e120a293427358a 192.168.33.159:7005
   slots: (0 slots) slave
   replicates 1761b5c929704f4b28577e8a45118265af3000ec
M: 2fb1ad83a7663a54eb873e99f69a02a678ec5fe1 192.168.33.159:7003
   slots:10923-16383 (5461 slots) master
   1 additional replica(s)
S: 8e822227ee657be7e781cfb9ad3057b0a20fe89f 192.168.33.159:7004
   slots: (0 slots) slave
   replicates f4becd9fda2f030d45894adf29299b713464deca
M: 1761b5c929704f4b28577e8a45118265af3000ec 192.168.33.159:7002
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: 0efa39d0ec0d487c8ed2b019ce977fc9b8c933fb 192.168.33.159:7006
   slots: (0 slots) slave
   replicates 2fb1ad83a7663a54eb873e99f69a02a678ec5fe1
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

連線redis叢集 

在192.168.33.159機器上進行連線

7001目錄下執行

./src/redis-cli -h 192.168.33.159 -c -p 7001

已經自動跳轉到了7002伺服器了

續

如果重啟伺服器後，再次執行redis-trib.rb會報錯如下錯誤：

[ERR] Node 192.168.33.159:7001 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.

解決方法：

刪除dump.rdb和nodes-7001.conf這兩個檔案，然後重啟redis服務，最後啟動叢集。

1次不行搞2次，2次不行搞3次。多刪除幾次