機能與靠得住性并聊包養網心得重,Flexus X 實例助力 Redis 三主三從集群高效運轉

華秋PCB

高靠得住多層板制造商

華秋SMT

高靠得住一站式PCBA智造商

華秋商城

自營現貨電子元器件商城

PCB Layo包養網心得ut

高多層、高密度產物design

鋼網制造

專注高品德鋼網制造

BOM配單

專門研究的一站式采購處理計劃

華秋DFM

一鍵剖析design隱患

華秋認證

認證檢測無可置疑


在尋求極致機能與靠得住性的途徑上,Flexus X 實例以出色的算力與智能調劑,為 Redis 三主三從集群的高效運轉保駕護航。此架構不只完成了數據的高可用性,還經由過程負載平衡晉陞了全體機能,確保您的營業在海量數據眼前仍然游刃有余。828 huawei云企業上云節,huawei云 Flexus X 實例聯袂 Redis 三主三從集群處理計劃,為您帶來史無前例的優惠與便捷,開啟數據庫高效運轉的新篇章!

鏈接中轉:huawei云Flexus云辦事器X實例

wKgZPGd88iaAcNayAAEA43MSbXE986.png

Redis 集群先容

Redis 三主三從集群是晉陞數據庫體系可用性、容錯性和機能的要害安排形式。它由三個主節點處置讀寫懇求,三個從節點復制主節點數據,確保數據高可用與冗余。經由過程主動毛病轉移機制,從節點能在主節點毛病時主動接收,保證辦事持續性。此外,讀寫分別與負載平衡戰略進一個步驟優化了體系機能,實用于電商、社交收集和及時數據剖析等高請求場景。

集群的焦點上風在于其高效的數據復制與同步機制,從節點無縫復制主節點數據,不梗阻主節點處置流程。同時,當主節點毛病時,體系能敏捷主動完成毛病轉移,無需人工干涉,極年夜晉陞了體系的穩固性和靠得住性。

Redis 三主三從集群以其出色的高可用性、容錯才能和機能優化,成為復雜利用場景下數據存儲與拜訪的首選計劃。經由過程公道設置裝備擺設與安排,它能有用知足各類營業對數據存儲的高請求,確保數據的平安、靠得住與高效拜訪。

官方網站:https://redis.io/

官方文檔:https://redis.io/docs/latest/

wKgZO2d88iaAA-FlAAUBjTqs1JE744.png

周遭的狀況計劃

安排流程

需求清楚:

•采用 docker 方法停止安排 Redis 三主三從集群

•具體購置設置裝備擺設實例可參考文章:疾速安排huawei云Fle包養sdxus X實例,開啟您的云端之旅

•安排 docker 辦事請參考文章:huaweiFlexusX與Docker+Nginx的高效整合之路

拉取鏡像

拉取鏡像并創立收集

[root@flexusx-251f~]# docker pull redis:6.0.86.0.8:Pulling 包養金額from library/redisbb79b6b2107f:Pull complete1ed3521a5dcb:Pull complete5999b99cee8f:Pull complete3f806f5245c9:Pull completef8a4497572b2:Pull completeeafe3b6b8d06:Pull completeDigest:sha256:21db12e5ab3cc343e9376d655e8eabbdbe5516801373e95a8a9e66010c5b8819Status:Downloaded new包養價格er image for redis:6.0.8docker.io/library/redis:6.0.8[root@flexusx-251f~]# docker network create redis-cluster-net4d9a413869dd2339ef196cf0b5611fbc6209d586c2c5fd5b2b8b8f02d1dd8203

安排主節點

[root@flexusx-251f~]# docker run -itd–nameredis-master1 –networkredis-cluster-net -p6379:6379 -v/data/redis/share/redis-node-1:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port637904c85ab05c718ace09a8eb56a77220edc9d068a5201125e23b3a222fc898c323[root@flexusx-251f~]# docker run -itd–nameredis-master2 –networkredis-cluster-net -p6380:6379 -v/data/redis/share/redis-nod包養網推薦e-2:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port6379a900e7ddf6c99313b4f1bfd068d8a6b735a4425ec3b055d5e0616a944bdd44e6[root@flexusx-251f~]# docker run -itd–nameredis-master3 –networkredis-cluster-net -p6381:6379 -v/data/redis/share/redis-node-3:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port6379

安排從節點

[root@flexusx-251f~]# docker run -itd–nameredis-slave1 –networkredis-cluster-net -p6382:6379 -v/data/redis/share/redis-slave-1:/data redis:6.0.8 –cluster-enable包養軟體dyes –appendonlyyes –port63797f39daa7c0a7a5ca221db4a3e02ec495c82e69d3131e32b968be2cf7be3a93a4[root@flexusx-251f~]# docker run -itd–nameredis-slave2 –networkredis-cluster-net -p6383:6379 -v/data/redis/share/redis-slave-2:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port63794e615a412d19072e4dd233f92f062867ab9bc8bf59587aa6252e2c1bc9796690[root@flexusx-251f~]# docker run -itd–nameredis-slave3 –networkredis-cluster-net -p6384:6379 -v/data/redis/share/redis-slave-3:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port637956693d453988d23f1d477867e4a7b7dba5b2e6b9fd8a80724ae0a14f5c4deead

初始化 redis 集群

放行端口 6379,6380,6381,6382,6383,6384

wKgZPGd88ieAKcppAAEJKWHCzYI212.png

檢查 Redis 主機 IP 地址

[root@flexusx-251f~]# docker inspect redis-master1 |grep-iipadd”SecondaryIPAddresses”:null,”IPAddress”:””,”IPAddress”:”172.27.0包養價格ptt.2″,[root@flexusx-251f~]# docker inspect redis-master2 |grep-iipadd”SecondaryIPAddresses”:null,”IPAddress”:””,”IPAddress”:”172.27.0.3″,[root@flexusx-251f~]# docker inspect redis-master3 |grep-iipadd”SecondaryIPAddresses”:null,”IPAddress”:””,”IPA包養犯法嗎ddress”:”172.27.0.7″,[root@flexusx-251f~]# docker inspect redis-slave1 |grep-iipadd”SecondaryIPAddresses”:null,”IPAddress”:””,”IPAddress”:”172.27.0.6″,[root@flexusx-251f~]# docker inspect redis-slave2 |grep-iipadd”SecondaryIPAddresses”:null,”IPAddress”:””,”IPAdd包養情婦ress”:”172.27.0.4″,[root@flexusx-251f~]# docker inspect redis-slave3 |grep-iipadd”S包養意思econdaryIPAddresses”:null,”IPAddress”:””,”IPAddress”:”172.27.0.5″,

進進此中一個主節點的容器外部

[root@flexusx-251f~]# docker e所以,她覺得躲起來是行不通的,只有坦誠的理解和接受,她才有未來。xec -itredis-master1 /bin/bash root@04c85ab05c71:/data#

留意將 ip 修正為本身的容器 ip,端口對應之前創立的節點 port

•在應用 redis-cli –cluster create號令創立 Redis 集群時,Redis 會主動依據供給的節點多少數字和 –cluster-replicas 1的參數來分派主節點和從節

[root@flexusx-251f~]# docker exec -itredis-master1 /bin/bash root@04c85ab05c71:/data#redis-cli –clustercreate 172.27.0.2:6379 172.27.0.3:6379 172.27.0.7:6379 172.27.0.6:6379 172.27.0.4:6379 172.27.0.5:6379 –cluster-replicas1

當呈現提醒“Can I set the above configuration? (type ‘yes’ to ac包養心得cept):”的時辰,輸出 yes 即可;

>>>Performing hashslots allocation on 6 nodes…Master[0]->Slots 0 -5460Master[1]->Slots 5461 -10922Master[2]->Slots 10923 -16383Addingreplica 172.27.0.4:包養網站6379 to 172.27.0.2:6379Addingreplica 172.27.0.5:6379 to 172.27.0.3:6379Addingreplica 172.27.0.6:6379 to 172.27.0.7:6379M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[0-5460](5461slots)masterM:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[5461-10922](5462slots)masterM:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[10923-16383](5461slots)masterS:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379replicates7921f3f2a93b319f0689f777“誰教你讀書讀書?”f108ea871215a8f9S:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379replicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379replicates3129“但這一次我不得不同意。”2a53e00a7613e37621404bb3b9fe3da79facCanI set the above configuration?(type’yes’to accept):yes

如許我們的三主三從就安排勝利了

wKgZO2d88ieAYKLpAADmZEpzLNs318.png

檢查集群狀況

第一種方法,肆意進進一個容器外部,然后進進 6379 端口的這個客戶端,-c 表現以集群的方法進進

[root@flexusx-251f~]# docker exec -itredis-master1 /bin/bash root@04c85ab05c71:/data#redis-cli -p6379 -c127.0.0.1:6379>cluster infocluster_state:ok #正常 cluster_slots_assigned:16384cluster_slots_ok:16384cluster_slots_pfail:0cluster_slots_fail:0cluster_known_nodes:6 # 6 節點 cluster_size:3cluster_current_epoch:6cluster_my_epoch:1cluster_stats_messages_ping_sent:269cluster_stats_messages_pong_sent:305cluster_stats_messages_sent:574cluster_stats_messages_ping_received:300cluster_stats_messages_pong_received:269cluster_stats_messages_meet_received:5cluster_stats_messages_received:574

第二種方法,經由過程 cluster nodes 檢查

[root@flexusx-251f~]# docker exec -itredis-master1 /bin/bash 127.0.0.1:6379>cluster nodes31292a53e00a7613e37621404bb3b9fe3da79fac172.27.0.3:6379@16379 master -0 1726211088655 2 connected 5461-1092224b3c498fa142da2e7f49f1c60dde9d7b49c8694172.27.0.2:6379@16379 myself,master -0 1726211087000 1 connected 0-54607921f3f2a93b319f0689f777f108ea871215a8f9172.27.0.7:6379@16379 master -0 1726211088000 3 connected 10923-16383ebebfbe22aafda4ab34621e336b87833229fb91b172.27.0.6:6379@16379 slave 7921f3f2a93b319f0689f777f108ea871215a8f9 0 1726211087654 3 connected8c3b43b00509c0a591862ed6ea561b873b0a5e他點了點頭。dd172.27.0.5:6379@16379 slave 31292a53e00a7613e37621404bb3b9fe3da79fac 0 1726211087000 2 connected0ed3f67915347da7146eece57f4f7d52c1393065172.27.0.4:6379@16379 slave 24b3c498fa142da2e7f49f1c60dde9d7b49c8694 0 1726211086000 1 connected

第三種方法,經由過程 redis-cli –cluster check 172.27.0.2:6379檢查(改成本身的 ip)

[root@flexusx-251f~]# docker exec -itredis-master1 /bin/bash root@04c85ab05c71:/data#redis-cli -p6379 -croot@04c85ab05c71:/data#redis-cli –clustercheck 172.27.0.2:6379172.27.0.2:6379(24b3c498…包養網站)->2 keys |5461slots |1slaves.172.27.0.3:6379(31292a53…)->0 keys |5462slots |1slaves.172.27.0.7:6379(7921f3f2…)->0 keys |5461slots |1slaves.[OK]2 keys in 3 masters.0.00keys per slot on average.>>>Performing ClusterCheck (usingnode 172.27.0.2:6379)M:24b3c498fa142da2e7f49f1c60dde9d的優勢。7b49c8694 172.27.0.2:6379slots:[0-5460](5461slots)master1additional replica(s)M:31292a53e00a包養網推薦7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[5461-10922](5462slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[10923-16383](5461slots)master1additional replica(s)S:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.

數據存儲測試

在主 ma包養合約ster2 節點上存數據

[root@flexusx-251f~]# docker exec -itredis-master2 /bin/ba包養一個月shroot@a900e7ddf6c9:/data#redis-cli -p6379 -c127.0.0.1:6379>set name zhangsanOK127.0.0.1:6379>set subject MathOK

在從 slave3 上檢查數據

[root@flexusx-251f~]# docker exec -itredis-slave3 /bin/bashroot@4bc3876d311b:/data#redis-cli -p6379 -c127.0.0.1:6379>get name->Redirected to slot [5798]located at 172.27.0.3:6379″zhangsan”172.27.0.3:6379>get subject”Math”

擴容測試

在創立兩臺節點容器

[root@flexusx-251f~]# docker run -itd–nameredis-master4 –networkredis-cluster-net -p6385:6379 -v/data/redis/share/redis-node-4:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port6379[root@flexusx-251f~]# doc甜心花園ker run -itd–nameredis-slave4 –networkredis-cluster-net -p6386:6379 -v/data/redis/share/redis-slave-4:/data redis:6.0.8 –cluster-enabledyes –appendonlyyes –port6379

檢查節點 ip 地址

[root@flexusx-251f~]# docker inspect redis-master4 |grep-iipadd “SecondaryIPAddresses”: null,”IPAd包養意思dress”:””,”IPAddress”:”172.27.0.8″,[root@flexusx-251f~]# docker inspect redis-slave4 |grep-iipadd”SecondaryIPAddresses”:null,”IPAddress”:””,”IPAddress”:”172.27.0.9″,

進進 redis-master4 節點,增添節點

[root@flexusx-251f~]# docker exec -itredis-master4 /bin/bashroot@b77caa384727:/data#redis-cli –clusteradd-node 172.27.0.8:6379 172.27.0.2:6379>>>Adding node172.27.0.8:6379 to cluster 172.27.0.2:6379>>>Performing ClusterCheck (usingnode 172.27.0.2:6379)M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[0-5460](5461slots)master1additional replica(s)M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[5461-10922](546包養女人2slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[10923-16383](5461slots)master1additional replica(s)S:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.>>>Send CLUSTERMEET to node 172.27.0.8:6379 to make it join the cluster.[OK]New node added correctly.

檢查主從狀況

•可以看到只要主節點,還未分派從節點

root@b77caa384727:/data#redis-cli –clustercheck 172.27.0.2:6379172.27.0.2:6379(24b3c498…)->2 keys |5461slots |1slaves.172.27.0.3:6379(31292a53…)->2 keys |5462slots |1slaves.172.27.0.7:6379(7921f3f2…)->0 keys |5461slots |1slaves.172.27.0.8:6379(290b2aa0…)->0 ke包養留言板ys |0slots |0slaves.[OK]4 keys in 4 masters.0.00keys per slot on average.>>>Performing ClusterCheck (usingnode 172.27.0.2:6379)M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[0-5460](5461slots)master1additional replica(s)M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[5461-10922](5462slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[10923-16383](5461slots)master1additional replica(s)S:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694M:290b2aa0e79a9c9ad5ebdb6aa468176b61513283 172.27.0.8:6379slots包養網dcard:(0slots)master[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.

槽位分派:172.27.0.8:6379 還沒有分派槽位

root@b77caa384727:/data#redis-cli –clusterreshard 172.27.0.2:6379>>>Performing ClusterCheck (using包養條件node 172.27.0.2:6379)M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[0-5460](5461slots)master1additional replica(s)M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[5461-10922](5462slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[10923-16383](5461slots)master1additional replica(s)S:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694M:290b2aa0e79a9c9ad5ebdb6aa468176b61513283 172.27.0.8:6379slots:(0slots)master[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.Howmany slots do you want to move (from1 to 16384)?4096Whatis the receiving node ID?290b2aa0e79a9c9ad5ebdb6aa468176b61513283Pleaseenter all the source node IDs.Type’all’to use all the nodes as source nodes for the hash slots.Type’done’once you entered all the source nodes IDs.Sourcenode #1: allReadyto move 4096 slots.Sourcenodes:M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[0-5460](5461slots)master1additional replica(s)M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[5461-10922](5462slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[10923-16383](5461slots)master1additional replica(s)Destinationnode:M:290b2aa0e79a9c9ad5ebdb6aa468176b61513283 172.27.0.8:6379slots:(0slots)masterReshardingplan:Movingslot 5461 from 31292a53e00a7613e37621404bb3b9fe3da79fac………….

檢查主從狀況

root@b77caa384727:/data#redis-cli –clustercheck 172.27.0.2:6379172.27.0.2:6379(24b3c498…)->1 keys |4096slots |1slaves.172.27.0台灣包養網.3:6379(31292a53…)->1 keys |4096slots |1slaves.172.27.0.7:6379(7921f3f2…)->0 keys |4096slots |1slaves.172.27.0.8:6379(290b2aa0…)->2 keys |4096slots |0slaves.[OK]4 keys in 4 masters.0.00keys per slot on average.>>>Performing ClusterCheck (usingnode 172.27.0.2:6379)M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[1365-5460](4096slots)master1additional replica(s)M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[6827-10922](4096slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[12288-16383](4096slots)master1additional replica(s)S:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S包養sd:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694M:290b2aa0e79a9c9ad5ebdb6aa468176b61513283 172.27.0.8:6379slots:[0-1364],[5461-6826],[10923-12287](4096slots)master[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.

為 172.27.0.8:6379 分派從節點 172.27.0.9:6379

# 172.27.0.8:6379 節點的 IDroot@b77caa384727:/data#redis-cli –clusteradd-node 172.27.0.9:6379 172.27.0.8:6379 –cluster-slave-包養犯法嗎-cluster-master-id290b2aa0e79a9c9ad5ebdb6aa468176b61513283>>>Adding node172.27.0.9:6379 to cluster 172.27.0.8:6379>>>Performing ClusterCheck (usingnode 172.27.0.8:6379)M:290b2aa0e79a9c9ad5ebdb6aa468176b61513283 172.27.0.8:6379slots:[0-1364],[5461-6826],[10923-12287](4096slots)masterM:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[1365-5460](4096slots)master1additional replica(s)M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[6827-10922](4096slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[12288-16383](4096slots)master1additional replica(s)S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.>>>Send CLUSTERMEET to node 172.27.0.9:6379 to make it join the cluster.Waitingfor the cluster to join>>>Configure nodeas replica 包養appof 172.27.0.8:6379.[OK]New node added correctly.

擴容完成

root@b77caa384727:/data#redis-cli –clustercheck 172.27.0.2:6379 172.27.0.2:6379(24b3c498…)->1 keys |4096slots |1slaves.172.27.0.3:6379(31292a53…)->1 keys |4096slots |1slaves.172.27.0.7:6379(7921f3f2…)->0 keys |4096slots |1slaves.172.27.0.8:6379(290b2aa0…)->2 keys |4096slots |1slaves.[OK]4 keys in 4 masters.0.00keys per slot on average.>>>Performing ClusterCheck (usingnode 172.27.0.2:6379)M:24b3c498fa142da2e7f49f1c60dde9d7b49c8694 172.27.0.2:6379slots:[1365-5460](4096slots)master1additional replica(s)S:c3abe3fa7ef3包養站長103d32e19f17c152250e3392c94f 172.27.0.9:6379slots:(0slots)slavereplicates290b2aa0e79a9c9ad5ebdb6aa468176b61513283M:31292a53e00a7613e37621404bb3b9fe3da79fac 172.27.0.3:6379slots:[6827-10922](4096slots)master1additional replica(s)M:7921f3f2a93b319f0689f777f108ea871215a8f9 172.27.0.7:6379slots:[12288-16383](4096slots)master1additional replica(s)S:ebebfbe22aafda4ab34621e336b87833229fb91b 172.27.0.6:6379slots:(0slots)slavereplicates7921f3f2a93b319f0689f777f108e包養違法a871215a8f9S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379slots:(0slots)slavereplicates31292a53e00a7613e37621404bb3b9fe3da79facS:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379slots:(0slots)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694M:290b2aa0e79a9c9ad5ebdb6aa468176b61513283 172.27.0.8:6379slot長期包養s:[0-1364],[5461-6826],[10923-12287](4096slots)master1additional replica(s)[OK]All nodes agree about slots configuration.>>>Check foropen slots…>>>Check slotscoverage…[OK]All 16384 slots covered.

體驗和感觸感染

huawei云 Flexus X 實例,以其出色的算力、機動的擴大性和智能的運維治理,為 Redis 三主三從集群的高效運轉供給了強無力的支持。Redis 三主三從集群,作為業界公認的高可用、高機能處理計劃,經由過程數據復制、主動毛病轉移和讀寫分別機制,確保了數據的平安性、分歧性和體系的穩固性。而huawei云 Flexus X 實例,憑仗其傑出的資本調劑才能和優化的收集架構,進一個步驟晉陞了集群的處置才能和呼應速率。

在 828 huawei云企業上云節,無論您是電商鉅子、社交收集前鋒,仍是及時數據剖析範疇的摸索者,Flexus X 都能助您一臂之力,讓數據成為驅動營業增加的焦點動力。點擊下方鏈接,當即舉動,讓 Flexus X 實例聯袂 Redis 三主三從集群,為您的數字化轉型之路加快護航!

產物鏈接:huawei云Flexus云辦事器X實例直播建站辦事器-huawei云

wKgZPGd88ieADNnOAAMdMY7jqCs214.png

審核編纂 黃宇


構建數據庫處理計劃,基于huawei云 Flexus X 實例容器化 MySQL 主從同步架構 huawei云企業上云節,Flexus X 實例特惠開啟,助力企業輕松構建高機能數據庫體系。專門研究團隊技巧支撐,確保安排無憂,運維 的頭像 頒發于 01-07 17:22 •32次瀏覽
云辦事器 Flexus X 實例:輕量級 http 辦事器 Tinyhttpd 安排 Flexus 云辦事器 X 實例 是huawei云發布的一款高機能、高靠得住性的云辦事器產物,它專為知足企業級用戶對盤算資本的嚴厲請求而design。本篇文章 的頭像 頒發于 01-07 16:59 •9次瀏覽
huawei云 Flexus X 實例 docker 安排 rancher 并構建 k8s 集群 · huawei云比來正在舉行 828 B2B 企業節,Flexus X 實例的促銷力度很是年夜,特殊合適那些對算力機能有高請求的小伙伴。假如你有自建 MySQL、 的頭像 頒發于 01-02 13:44 •62次瀏覽
Flexus X 實例在huawei云 EulerOS 周遭的狀況中安排碉堡機 Jumpserver 的具體指南 媒介 “捉住huawei云 828 B2B 企業節優惠,Flexus X 實例助力高機能盤算需求—包養意思—體驗 Jumpserver 碉堡機的流利 的頭像 頒發于 01-02 13:43 •57次瀏覽
huawei云 Flexus 云辦事器 X 實例安排 Note Mark 筆記東西 可以或許充足應用其出色的盤算才能,確保利用運轉流利,更能依托其穩固靠得住的云辦事體驗,完成高效、便捷且平安的數據治理,開啟小我信息化治理的新篇章! 一、Flexus 云辦事器 的頭像 頒發于 01-02 13:42 •58次瀏覽
huawei云Flexus X實例,Redis機能加快評測及對照 跟著云盤算技巧的飛速成長,Redis 作為一種高機能的內存數據庫,在各類利用場景中施展著越來越主要的感化。為了知足分歧用戶對 Redis 機能的高請求,huawei云發布了 的頭像 頒發于 12-29 15:47 •17“20天過去了,他還沒有發來關心的字眼。即使席家來提出要他離婚,他也沒有動,也沒有表現出什麼,萬一女兒還不能呢?1次瀏覽
深度評測,huawei云 Flexus X 實例在 Sysbench 機能測試中的亮眼表示 了出色的才能。經由過程 Sysbench 的詳盡測試,Flexus X 實例在多核盤算才能、內存吞吐量、磁盤呼應速率及吞吐才能方面均取得了高分。其高主頻、多核支撐以及智能資本分配機制,確保了在各類任務負載下的穩固 的頭像 頒發于 12-27 13:47 •110次瀏覽
huawei云 Flexus X 輕松完成 Redis 一主多從高效安排 購置實例、設置裝備擺設 Redis 主從節點,并驗證一主多從架構的對的性。經由過程現實操縱,您將體驗到 Flexus 的頭像 頒發于 12-27 13:45 •185次瀏覽
云辦事器 Flexus X 實例:安排 AgentOps,全方位監測智能體 經由過程深刻體驗huawei云的 Flexus 云辦事器包養一個月 X 實例,我發明它不只供給了直接經由過程公網拜訪的方便性,還支撐高效的內在的事務復制粘貼效能,使得操縱更 的頭像 頒發于 12-26 18:10 •135次瀏覽
基于huawei云 Flexus 云辦事女大生包養俱樂部器 X 實例部搭建 Halo 博客平臺 署 Halo 博客平臺,充足施展其穩固靠得住的云辦事上風。經由過程這一實行,我們將展現若何應用huawei云的強盛支撐,完成博客平臺的高效搭建與治理。依托huawei云 Flexus 云辦事器 X 的頭像 頒發于 12-26 09:40 •164次瀏覽
huawei云 Flexus X 實例 MySQL 機能加快評測及對照 場景需求 3 二、Flexus 云辦事器 X 購置 3 2.1 Flexus X 實例購置 4 2.2 購置 MySQL 加快鏡像 4 2. 的頭像 頒發于 12-25 17:10 •183次瀏覽
基于huawei云 Flexus 云辦事器 X 實例搭建 Linux 進修周遭的狀況 不只供給了強盛的盤算資本,還擁有機動的擴大才能和穩固的運轉表示,為用戶供給了靠得住的技巧支持。特殊是對于那些盼望疾速搭建 Linux 進修周遭的狀況的用戶來說,huawei云 Flexus 云辦事器 X 的頭像 頒發于 12-25 17:10 •162次瀏覽
Flexus X 實例 CPU、內存及磁盤機能實測與剖析 引言 跟著云盤算的普及,企業對于云資本的需求日益增添,而選擇一款機能微弱、穩固性高的云實例成為了要害。huawei云 Flexus X 實例作為huawei 的頭像 頒發于 12-24 17:35 •183次瀏覽
huawei Flexus 云辦事器 X 實例 應用流程 評測與利用體驗:高機能與經濟性的完善聯合引言在云盤算範疇,彈性算力的需求日益增加。傳統云辦事器凡是供給固定的規格,招致資本揮霍和不婚配的機能題目。huawei云發布的 Flexus 云辦事器 的頭像 頒發于 12-24 17:28 •157次瀏覽
機能高達 6 倍,Flexus X 實例用實力論述什么是新一代柔性算力 X 實例(以下簡稱:Flexus X 實例)憑仗其前沿的機能和立異技巧,正在加快行業變更,引領 的頭像 頒發于 07-03 15:43 •673次瀏覽

發佈留言

發佈留言必須填寫的電子郵件地址不會公開。 必填欄位標示為 *