国产精品久久久aaaa,日日干夜夜操天天插,亚洲乱熟女香蕉一区二区三区少妇,99精品国产高清一区二区三区,国产成人精品一区二区色戒,久久久国产精品成人免费,亚洲精品毛片久久久久,99久久婷婷国产综合精品电影,国产一区二区三区任你鲁

0
  • 聊天消息
  • 系統消息
  • 評論與回復
登錄后你可以
  • 下載海量資料
  • 學習在線課程
  • 觀看技術視頻
  • 寫文章/發帖/加入社區
會員中心
創作中心

完善資料讓更多小伙伴認識你,還能領取20積分哦,立即完善>

3天內不再提示

性能與可靠性并重,Flexus X 實例助力 Redis 三主三從集群高效運行

jf_21561199 ? 來源:jf_21561199 ? 作者:jf_21561199 ? 2025-01-07 17:21 ? 次閱讀
加入交流群
微信小助手二維碼

掃碼添加小助手

加入工程師交流群

前言

在追求極致性能與可靠性的道路上,Flexus X 實例以卓越的算力與智能調度,為 Redis 三主三從集群的高效運行保駕護航。此架構不僅實現了數據的高可用性,還通過負載均衡提升了整體性能,確保您的業務在海量數據面前依然游刃有余。828 華為云企業上云節,華為云 Flexus X 實例攜手 Redis 三主三從集群解決方案,為您帶來前所未有的優惠與便捷,開啟數據庫高效運行的新篇章!

鏈接直達華為云Flexus云服務器X實例

wKgZPGd88iaAcNayAAEA43MSbXE986.png

Redis 集群介紹

Redis 三主三從集群是提升數據庫系統可用性、容錯性和性能的關鍵部署模式。它由三個主節點處理讀寫請求,三個從節點復制主節點數據,確保數據高可用與冗余。通過自動故障轉移機制,從節點能在主節點故障時自動接管,保障服務連續性。此外,讀寫分離與負載均衡策略進一步優化了系統性能,適用于電商、社交網絡和實時數據分析等高要求場景。

集群的核心優勢在于其高效的數據復制與同步機制,從節點無縫復制主節點數據,不阻塞主節點處理流程。同時,當主節點故障時,系統能迅速自動完成故障轉移,無需人工干預,極大提升了系統的穩定性和可靠性。

Redis 三主三從集群以其卓越的高可用性、容錯能力和性能優化,成為復雜應用場景下數據存儲與訪問的首選方案。通過合理配置與部署,它能有效滿足各類業務對數據存儲的高要求,確保數據的安全、可靠與高效訪問。

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

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

wKgZO2d88iaAA-FlAAUBjTqs1JE744.png

環境規劃

部署流程

需要了解:

?采用 docker 方式進行部署 Redis 三主三從集群

?詳細購買配置實例可參考文章:快速部署華為云Flexus X實例,開啟您的云端之旅

?部署 docker 服務請參考文章:華為FlexusX與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 newer 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-node-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-enabledyes --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.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":"","IPAddress":"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":"","IPAddress":"172.27.0.4",[root@flexusx-251f~]# docker inspect redis-slave3 |grep-iipadd"SecondaryIPAddresses":null,"IPAddress":"","IPAddress":"172.27.0.5",

進入其中一個主節點的容器內部

[root@flexusx-251f~]# docker exec -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 accept):”的時候,輸入 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:6379replicates7921f3f2a93b319f0689f777f108ea871215a8f9S:0ed3f67915347da7146eece57f4f7d52c1393065 172.27.0.4:6379replicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694S:8c3b43b00509c0a591862ed6ea561b873b0a5edd 172.27.0.5:6379replicates31292a53e00a7613e37621404bb3b9fe3da79facCanI 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 connected8c3b43b00509c0a591862ed6ea561b873b0a5edd172.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: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)slavereplicates24b3c498fa142da2e7f49f1c60dde9d7b49c8694[OK]All nodes agree about slots configuration.>>>Check foropen slots...>>>Check slotscoverage...[OK]All 16384 slots covered.

數據存儲測試

在主 master2 節點上存數據

[root@flexusx-251f~]# docker exec -itredis-master2 /bin/bashroot@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~]# docker 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,"IPAddress":"","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](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.>>>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 keys |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:(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 (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:(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: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 of 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:c3abe3fa7ef3103d32e19f17c152250e3392c94f 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)slavereplicates7921f3f2a93b319f0689f777f108ea871215a8f9S: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)master1additional replica(s)[OK]All nodes agree about slots configuration.>>>Check foropen slots...>>>Check slotscoverage...[OK]All 16384 slots covered.

體驗和感受

華為云 Flexus X 實例,以其卓越的算力、靈活的擴展性和智能的運維管理,為 Redis 三主三從集群的高效運行提供了強有力的支撐。Redis 三主三從集群,作為業界公認的高可用、高性能解決方案,通過數據復制、自動故障轉移和讀寫分離機制,確保了數據的安全性、一致性和系統的穩定性。而華為云 Flexus X 實例,憑借其出色的資源調度能力和優化的網絡架構,進一步提升了集群的處理能力和響應速度。

在 828 華為云企業上云節,無論您是電商巨頭、社交網絡先鋒,還是實時數據分析領域的探索者,Flexus X 都能助您一臂之力,讓數據成為驅動業務增長的核心動力。點擊下方鏈接,立即行動,讓 Flexus X 實例攜手 Redis 三主三從集群,為您的數字化轉型之路加速護航!

產品鏈接華為云Flexus云服務器X實例直播建站服務器-華為云

wKgZPGd88ieADNnOAAMdMY7jqCs214.png

審核編輯 黃宇

聲明:本文內容及配圖由入駐作者撰寫或者入駐合作網站授權轉載。文章觀點僅代表作者本人,不代表電子發燒友網立場。文章及其配圖僅供工程師學習之用,如有內容侵權或者其他違規問題,請聯系本站處理。 舉報投訴
  • 華為云
    +關注

    關注

    3

    文章

    2832

    瀏覽量

    19247
收藏 人收藏
加入交流群
微信小助手二維碼

掃碼添加小助手

加入工程師交流群

    評論

    相關推薦
    熱點推薦

    什么是高可靠性

    滿足后續PCBA裝配的生產條件,并在特定的工作環境和操作條件下,在一定的時期內,可以保持正常運行功能的能力。 二、為什么PCB的高可靠性應當引起重視? 作為各種電子元器件的載體和電路信號傳輸的樞紐
    發表于 01-29 14:49

    德州儀器ISO772x數字隔離器:高性能與可靠性的完美結合

    德州儀器ISO772x數字隔離器:高性能與可靠性的完美結合 在電子設計領域,數字隔離器是保障系統安全和穩定運行的關鍵組件之一。德州儀器(Texas Instruments)的ISO77
    的頭像 發表于 01-22 17:20 ?583次閱讀

    ISO772x數字隔離器:高性能與可靠性的完美結合

    ISO772x數字隔離器:高性能與可靠性的完美結合 在電子工程師的日常設計工作中,數字隔離器是保障系統安全、穩定運行的關鍵組件。今天,我們就來深入探討一下德州儀器(Texas Inst
    的頭像 發表于 01-22 17:20 ?735次閱讀

    ISO164x系列I2C隔離器:高性能與可靠性的完美結合

    ISO164x系列I2C隔離器:高性能與可靠性的完美結合 在電子設計領域,I2C總線作為一種廣泛應用的通信接口,連接著各種主設備和設備。然而,為了確保系統的穩定性和安全
    的頭像 發表于 01-21 15:05 ?181次閱讀

    ISO672x-Q1汽車數字隔離器:高性能與可靠性的完美結合

    ISO672x-Q1汽車數字隔離器:高性能與可靠性的完美結合 在電子工程師的日常設計工作中,隔離器是確保系統安全、穩定運行的關鍵組件之一。今天,我們就來深入探討一下德州儀器(TI)推出
    的頭像 發表于 01-21 11:10 ?372次閱讀

    ISO642x數字隔離器:高性能與可靠性兼備的理想之選

    ISO642x數字隔離器:高性能與可靠性兼備的理想之選 在電子設計領域,數字隔離器是保障系統安全和穩定運行的關鍵組件。今天,我們來深入探討ISO642
    的頭像 發表于 01-19 16:20 ?423次閱讀

    MUN12AD03-SEC電源模塊性能、成本、可靠性大優勢

    MUN12AD03-SEC電源模塊性能、成本、可靠性大優勢隨著工業4.0、5G通信和AIoT的快速發展,電源模塊正從‘功能組件”向‘系統核心’演進。客戶對效率、集成度和可靠性的要求已
    發表于 01-15 09:50

    TMUX721x系列開關:高性能與可靠性的完美結合

    TMUX721x系列開關:高性能與可靠性的完美結合 在電子設計領域,選擇合適的開關器件對于實現系統的高性能可靠性至關重要。TMUX721
    的頭像 發表于 01-13 10:45 ?332次閱讀

    Amphenol MLC Rugged Metal LC Connectors:高性能與可靠性的完美結合

    Amphenol MLC Rugged Metal LC Connectors:高性能與可靠性的完美結合 在電子工程領域,連接器的性能可靠性至關重要,尤其是在軍事、工業等高要求的應
    的頭像 發表于 12-10 10:25 ?451次閱讀

    深度解析SLM345CK-DG 40V, 1.0 A 高性能、高可靠性兼容光耦的隔離柵極驅動器

    傳統光耦驅動器的管腳,卻在性能可靠性上實現了顯著飛躍,是升級現有光耦驅動方案的理想選擇。 一、核心優勢:超越光耦的性能與可靠性SLM34x
    發表于 07-21 08:56

    Redis集群部署配置詳解

    Redis集群是一種分布式Redis解決方案,通過數據分片和主從復制實現高可用和橫向擴展。集群將整個數據集分割成16384個哈希槽(has
    的頭像 發表于 07-17 11:04 ?978次閱讀

    Redis集群部署與性能優化實戰

    Redis作為高性能的內存數據庫,在現代互聯網架構中扮演著關鍵角色。作為運維工程師,掌握Redis的部署、配置和優化技能至關重要。本文將從實戰角度出發,詳細介紹Redis
    的頭像 發表于 07-08 17:56 ?847次閱讀

    分立器件可靠性工業死機到汽車故障的隱形防線

    本文聚焦分立器件可靠性,指出35%電子設備失效源于選型不當。解析可靠性大核心指標(標準認證、參數分析、實測驗證)及選型大黃金法則,強調避免常溫參數忽視、盲目進口等誤區。合科泰器件適
    的頭像 發表于 04-23 13:16 ?861次閱讀
    分立器件<b class='flag-5'>可靠性</b>:<b class='flag-5'>從</b>工業死機到汽車故障的隱形防線

    M12 航空插頭:高性能與可靠性的完美融合

    德索精密工業的 M12 航空插頭通過高性能與可靠性的完美融合,在工業自動化、軌道交通、汽車制造、智能儀器儀表等眾多領域發揮著不可替代的作用,為各類設備的穩定運行高效數據傳輸提供了堅實
    的頭像 發表于 04-01 11:38 ?732次閱讀
    M12 航空插頭:高<b class='flag-5'>性能與</b><b class='flag-5'>可靠性</b>的完美融合

    redis集群方案詳解

    Redis中提供的集群方案總共有種(一般一個redis節點不超過10G內存)。
    的頭像 發表于 03-31 10:46 ?1529次閱讀
    <b class='flag-5'>redis</b><b class='flag-5'>三</b>種<b class='flag-5'>集群</b>方案詳解