Linux下Redis叢集搭建與測試
阿新 • • 發佈:2018-12-25
叢集搭建
準備條件
一臺已經配置好Redis服務的虛擬機器,地址為:
192.168.2.100:6379
克隆6臺,使用命令nmtui
修改地址分別為:
192.168.2.101
192.168.2.102
192.168.2.103
192.168.2.104
192.168.2.105
192.168.2.106
由於叢集的容錯機制是超過半數的節點認為某節點掛掉就確認掛掉,因此我們搭建的叢集最好是奇數臺(>=3)。又由於為了高可用性,每個節點需要有備份節點,因此我們搭建Redis叢集至少要有6臺虛擬機器。
然後用Xshell連上,進行已下操作:
選擇全部Xshell
開始配置
主機為192.168.2.100
,修改redis.conf檔案:
daemonize yes # 作為後臺執行
cluster-enabled yes # 開啟叢集
六臺虛擬機器的這兩項配置都一樣,因此我們把剛修改好的這份配置檔案複製到其它5臺虛擬機器上。
scp /etc/redis/6379.conf 192.168.2.101:/etc/redis/6379.conf;scp /etc/redis/6379.conf 192.168.2.102:/etc/redis/6379.conf;scp /etc/redis/6379.conf 192.168.2.103 :/etc/redis/6379.conf;scp /etc/redis/6379.conf 192.168.2.104:/etc/redis/6379.conf; scp /etc/redis/6379.conf 192.168.2.105:/etc/redis/6379.conf;scp /etc/redis/6379.conf 192.168.2.106:/etc/redis/6379.conf
可能會提示,輸入yes
,之後輸入使用者名稱和密碼即可。
安裝ruby環境
以下命令都在
中執行
安裝RVM
$gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7 D2BAF1CF37B13E2069D6956105BD0E739499BDB
$\curl -sSL https://get.rvm.io | bash -s stable
使用RVM安裝Ruby
rvm install ruby 2.4.2
安裝RubyGems(ruby第三方包管理工具)
$ gem sources --add https://gems.ruby-china.org/ --remove https://rubygems.org/
$ gem sources -l
https://gems.ruby-china.org
# 確保只有 gems.ruby-china.org
最後執行:
$gem update --system
$gem -v
安裝gem redis
在主機192.168.2.100
執行:
gem install redis
然後將redis-trib.rb
複製到/usr/local/bin
目錄下:
cp /usr/local/redis-4.0.2/src/redis-trib.rb /usr/local/bin
正式搭建叢集
在主機192.168.2.100
執行:
redis-trib.rb create --replicas 1 192.168.2.101:6379 192.168.2.102:6379 192.168.2.102:6379 192.168.2.103:6379 192.168.2.104:6379 192.168.2.105:6379 192.168.2.106:6379 192.168.2.107:6379
如果出現錯誤:
[ERR] Node 192.168.2.101:6379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.
解決辦法,所有主機都執行以下命令:
$redis-cli
$flushdb
如果出現錯誤:
/usr/local/rvm/gems/ruby-2.4.2/gems/redis-4.0.1/lib/redis/client.rb:119:in `call': ERR Slot 1151 is already busy (Redis::CommandError)
from /usr/local/rvm/gems/ruby-2.4.2/gems/redis-4.0.1/lib/redis.rb:2764:in `block in method_missing'
from /usr/local/rvm/gems/ruby-2.4.2/gems/redis-4.0.1/lib/redis.rb:45:in `block in synchronize'
from /usr/local/rvm/rubies/ruby-2.4.2/lib/ruby/2.4.0/monitor.rb:214:in `mon_synchronize'
from /usr/local/rvm/gems/ruby-2.4.2/gems/redis-4.0.1/lib/redis.rb:45:in `synchronize'
from /usr/local/rvm/gems/ruby-2.4.2/gems/redis-4.0.1/lib/redis.rb:2763:in `method_missing'
from /usr/local/bin/redis-trib.rb:212:in `flush_node_config'
from /usr/local/bin/redis-trib.rb:776:in `block in flush_nodes_config'
from /usr/local/bin/redis-trib.rb:775:in `each'
from /usr/local/bin/redis-trib.rb:775:in `flush_nodes_config'
from /usr/local/bin/redis-trib.rb:1296:in `create_cluster_cmd'
from /usr/local/bin/redis-trib.rb:1700:in `<main>'
解決辦法,所有主機都執行以下命令:
$redis-cli
$flushall
$cluster reset soft
$exit
出現下圖表示配置成功:
可以看到主機:
192.168.2.101
192.168.2.102
192.168.2.103
是主庫
主機:
192.168.2.104
192.168.2.105
192.168.2.106
是從庫,且192.168.2.104
是192.168.2.101
的從庫。
192.168.2.105
是192.168.2.102
的從庫。
192.168.2.106
是192.168.2.103
的從庫。
且
slots:0-5460被分配到192.168.2.101
,
slots:5461-10922被分配到192.168.2.102
,
slots:10923-16383被分配到192.168.2.103
。
叢集測試
執行命令:
redis-cli -h 192.168.2.104 -p 6379 -c
-c
:表示重定向
192.168.2.104:6379> set key104 hello104
-> Redirected to slot [5860] located at 192.168.2.102:6379
OK
192.168.2.102:6379> get key104
"hello104"
檢視叢集資訊:
cluster info
192.168.2.102:6379> cluster info
cluster_state:ok # 叢集狀態
cluster_slots_assigned:16384 # 已分配的插槽數量
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0 # 插槽分配失敗的數量
cluster_known_nodes:6 # 已知節點數
cluster_size:3 # 叢集數量
cluster_current_epoch:6
cluster_my_epoch:2
cluster_stats_messages_ping_sent:3321
cluster_stats_messages_pong_sent:3271
cluster_stats_messages_meet_sent:5
cluster_stats_messages_sent:6597
cluster_stats_messages_ping_received:3271
cluster_stats_messages_pong_received:3326
cluster_stats_messages_received:6597
檢視節點資訊:
cluster nodes
192.168.2.102:6379> cluster nodes
c66496e74fa73e97474fb7c5083a4343ddf82700 192.168.2.103:6379@16379 master - 0 1512714933000 3 connected 10923-16383
75cb9a7cb353edc184bb75a31478d0bf428f7f50 192.168.2.101:6379@16379 master - 0 1512714932000 1 connected 0-5460
d1be0e6e88d2dc4f4798a60a9954a3727864eb86 192.168.2.106:6379@16379 slave c66496e74fa73e97474fb7c5083a4343ddf82700 0 1512714934674 6 connected
ff74ee17d417a8e424210d4223597dcb7205be51 192.168.2.104:6379@16379 slave 75cb9a7cb353edc184bb75a31478d0bf428f7f50 0 1512714931000 4 connected
077d5522363a210b56ae9b1abe8116da78b05263 192.168.2.105:6379@16379 slave e986f608ffd3b569471d32557b208487e995ec56 0 1512714934000 5 connected
e986f608ffd3b569471d32557b208487e995ec56 192.168.2.102:6379@16379 myself,master - 0 1512714934000 2 connected 5461-10922
參考: