2. 程式人生 > 其它 >10.Ceph 基礎篇 - RGW 高可用

10.Ceph 基礎篇 - RGW 高可用

阿新 • • 發佈：2022-03-26

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485316&idx=1&sn=d3a6be417aa39bb03d3fc8bf61527a2a&chksm=e9fdd270de8a5b66940ffe07e58535acfa88ebb8342d52510eefee8eba30dbecaa225122de25&cur_album_id=1600845417376776197&scene=189#wechat_redirect

RGW 擴充套件

1.叢集狀態

[root@ceph-node01 ~]# ceph -s
  cluster:
    id: cc10b0cb-476f-420c-b1d6-e48c1dc929af
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum ceph-node01,ceph-node02,ceph-node03 (age 7h)
    mgr: ceph-node01(active, since 7d), standbys: ceph-node03, ceph-node02
    osd: 7 osds: 7 up (since 7h), 7 in (since 44h)
    rgw: 1 daemon active (ceph-node01)

  task status:

  data:
    pools: 7 pools, 224 pgs
    objects: 1.14k objects, 2.9 GiB
    usage: 16 GiB used, 784 GiB / 800 GiB avail
    pgs: 224 active+clean

[root@ceph-node01 ~]#

通過ceph -s 可以看到，目前只有一個radosgw程序；

2.擴充套件rgw閘道器

[root@ceph-node01 ceph-deploy]# ceph-deploy rgw create ceph-node02
[ceph_deploy.conf][DEBUG ] found configuration file at: /root/.cephdeploy.conf
[ceph_deploy.cli][INFO ] Invoked (2.0.1): /usr/bin/ceph-deploy rgw create ceph-node02
[ceph_deploy.cli][INFO ] ceph-deploy options:
[ceph_deploy.cli][INFO ] username : None
[ceph_deploy.cli][INFO ] verbose : False
[ceph_deploy.cli][INFO ] rgw : [('ceph-node02', 'rgw.ceph-node02')]
[ceph_deploy.cli][INFO ] overwrite_conf : False
[ceph_deploy.cli][INFO ] subcommand : create
[ceph_deploy.cli][INFO ] quiet
。。。
[root@ceph-node01 ceph-deploy]#

這樣部署完成後，預設監聽在7480埠上面，下面我們修改配置；

3.新增配置檔案

[root@ceph-node01 ceph-deploy]# cat ceph.conf
。。。

[client.rgw.ceph-node01]
rgw_frontends = "civetweb port=80"
[client.rgw.ceph-node02]
rgw_frontends = "civetweb port=80"

。。。
[root@ceph-node01 ceph-deploy]#

4.推送配置檔案

[root@ceph-node01 ceph-deploy]# ceph-deploy --overwrite-conf config push ceph-node01 ceph-node02 ceph-node03^C

5.重啟radosgw服務

[root@ceph-node02 ~]# systemctl restart ceph-radosgw.target

需要ssh到 ceph-node02上面進行伺服器重啟；

RGW 高可用

架構圖

伺服器規劃

由於測試叢集，伺服器數量有限，我們只是使用keepalived與haproxy都共用ceph-node01與ceph-node02，如果有額外的機器，可以不共用。

radosgw 埠修改

# 1. 修改配置
[root@ceph-node01 ceph-deploy]# cat ceph.conf
。。。

[client.rgw.ceph-node01]
rgw_frontends = "civetweb port=81"
[client.rgw.ceph-node02]
rgw_frontends = "civetweb port=81"

[osd]
osd crush update on start = false

# 2. 推送配置
[root@ceph-node01 ceph-deploy]# ceph-deploy --overwrite-conf config push ceph-node01 ceph-node02 ceph-node03
。。。
[root@ceph-node01 ceph-deploy]#

# 3. 重啟ceph-node01 rgw 服務並檢視監聽
[root@ceph-node01 ceph-deploy]# systemctl restart ceph-radosgw.target
[root@ceph-node01 ceph-deploy]# netstat -antp |grep 81|grep radosgw
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 85707/radosgw
[root@ceph-node01 ceph-deploy]# ssh ceph-node02
Last login: Sat Oct 17 06:28:17 2020 from 100.73.18.152

# 4. 重啟ceph-node02 rgw 服務並檢視監聽
[root@ceph-node02 ~]# systemctl restart ceph-radosgw.target
[root@ceph-node02 ~]# netstat -antp |grep radosgw |grep 81
tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 11222/radosgw
[root@ceph-node02 ~]#
[root@ceph-node02 ~]# exit
登出
Connection to ceph-node02 closed.
[root@ceph-node01 ceph-deploy]#

部署keepalived

ceph-node01節點：

# 1. ceph-node01 安裝
[root@ceph-node01 ~]# yum -y install keepalived

# 2. 配置檔案
[root@ceph-node01 keepalived]# cat /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   notification_email {
     [email protected]
     [email protected]
     [email protected]
   }
   notification_email_from [email protected]
   smtp_server 192.168.200.1
   smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script haproxy_check {
  script "killall -0 haproxy"
  interval 2
  weight -2
}
vrrp_instance RADOSGW {
    state MASTER
    interface eth0
    virtual_router_id 54
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        100.73.18.253/24
    }

    track_script {
  haproxy_check
    }
}
[root@ceph-node01 keepalived]#

# 3. 啟動
[root@ceph-node01 keepalived]# systemctl start keepalived && systemctl enable keepalived

ceph-node02節點：

# 1. ceph-node02 安裝
[root@ceph-node02 ~]# yum -y install keepalived

# 2. 配置檔案
[root@ceph-node02 ~]# cat /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   notification_email {
     [email protected]
     [email protected]
     [email protected]
   }
   notification_email_from [email protected]
   smtp_server 192.168.200.1
   smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   vrrp_strict
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script haproxy_check {
  script "killall -0 haproxy"
  interval 2
  weight -2
}
vrrp_instance RADOSGW {
    state BACKUP
    interface eth0
    virtual_router_id 54
    priority 99
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        100.73.18.253/24
    }

    track_script {
  haproxy_check
    }
}
[root@ceph-node02 ~]#

# 3. 啟動
[root@ceph-node02 keepalived]# systemctl start keepalived && systemctl enable keepalived

keepalived 兩個節點之間，只有state與priority 權重的區別，其它都一樣；

遇到問題

Oct 19 09:34:30 ceph-node01 Keepalived_vrrp[87655]: VRRP_Instance(RADOSGW) ignoring received advertisment...
Oct 19 09:34:31 ceph-node01 Keepalived_vrrp[87655]: (RADOSGW): ip address associated with VRID 51 not present in MASTER advert : 100.73.18.253
Oct 19 09:34:31 ceph-node01 Keepalived_vrrp[87655]: bogus VRRP packet received on eth0 !!!
Oct 19 09:34:31 ceph-node01 Keepalived_vrrp[87655]: VRRP_Instance(RADOSGW) ignoring received advertisment...
Oct 19 09:34:32 ceph-node01 Keepalived_vrrp[87655]: (RADOSGW): ip address associated with VRID 51 not present in MASTER advert : 100.73.18.253
Oct 19 09:34:32 ceph-node01 Keepalived_vrrp[87655]: bogus VRRP packet received on eth0 !!!
Oct 19 09:34:32 ceph-node01 Keepalived_vrrp[87655]: VRRP_Instance(RADOSGW) ignoring received advertisment...
Oct 19 09:34:33 ceph-node01 Keepalived_vrrp[87655]: (RADOSGW): ip address associated with VRID 51 not present in MASTER advert : 100.73.18.253
Oct 19 09:34:33 ceph-node01 Keepalived_vrrp[87655]: bogus VRRP packet received on eth0 !!!

原因：當前 keepalived 叢集的 backup 節點收到的包中的 ip 地址與當前節點的虛擬 ip 地址不匹配，造成這種情況通常是當前網路內還有另外一組keepalived叢集，virtual_router_id與當前叢集的重複，嘗試修改到0-255的其他值，避免衝突，這裡由51修改成54解決；

檢視VIP

[root@ceph-node01 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 06:bb:14:00:0a:8c brd ff:ff:ff:ff:ff:ff
    inet 100.73.18.152/24 brd 100.73.18.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 100.73.18.253/24 scope global secondary eth0
       valid_lft forever preferred_lft forever
[root@ceph-node01 ~]# ping 100.73.18.253 -c 1
PING 100.73.18.253 (100.73.18.253) 56(84) bytes of data.


^C
--- 100.73.18.253 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

[root@ceph-node01 ~]#

關閉過濾規則

[root@ceph-node01 ~]# iptables -t filter -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP all -- 0.0.0.0/0 100.73.18.253

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root@ceph-node01 ~]#
[root@ceph-node01 ~]# iptables -t filter -F
[root@ceph-node01 ~]# iptables -t filter -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root@ceph-node01 ~]#
[root@ceph-node01 ~]# ping 100.73.18.253 -c 2
PING 100.73.18.253 (100.73.18.253) 56(84) bytes of data.
64 bytes from 100.73.18.253: icmp_seq=1 ttl=64 time=0.018 ms
64 bytes from 100.73.18.253: icmp_seq=2 ttl=64 time=0.022 ms

--- 100.73.18.253 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.018/0.020/0.022/0.002 ms
[root@ceph-node01 ~]#

部署haproxy

# 1. ceph-node01 與 ceph-node02 均安裝haproxy
[root@ceph-node01 haproxy]# yum -y install haproxy

# 2. 配置檔案
[root@ceph-node01 keepalived]# cat /etc/haproxy/haproxy.cfg
global
    log 127.0.0.1 local2

    chroot /var/lib/haproxy
    pidfile /var/run/haproxy.pid
    maxconn 4000
    user haproxy
    group haproxy
    daemon

    stats socket /var/lib/haproxy/stats

defaults
    mode http
    log global
    option httplog
    option dontlognull
    option http-server-close
    option forwardfor except 127.0.0.0/8
    option redispatch
    retries 3
    timeout http-request 10s
    timeout queue 1m
    timeout connect 10s
    timeout client 1m
    timeout server 1m
    timeout http-keep-alive 10s
    timeout check 10s
    maxconn 3000

frontend http_web *:80
    mode http
    default_backend radosgw

backend radosgw
    balance roundrobin
    mode http
    server ceph-node01 100.73.18.152:81
    server ceph-node02 100.73.18.153:81

[root@ceph-node01 keepalived]#

# 3. 啟動
[root@ceph-node01 haproxy]# systemctl enable haproxy && systemctl start haproxy
Created symlink from /etc/systemd/system/multi-user.target.wants/haproxy.service to /usr/lib/systemd/system/haproxy.service.

# 4. 啟動 ceph-node02
[root@ceph-node01 haproxy]# scp /etc/haproxy/haproxy.cfg ceph-node02:/etc/haproxy/
haproxy.cfg 100% 992 3.3MB/s 00:00
[root@ceph-node01 haproxy]# ssh ceph-node02
Last login: Mon Oct 19 09:22:57 2020 from 100.73.18.152
[root@ceph-node02 ~]# systemctl enable haproxy && systemctl start haproxy
Created symlink from /etc/systemd/system/multi-user.target.wants/haproxy.service to /usr/lib/systemd/system/haproxy.service.
[root@ceph-node02 ~]#

驗證

[root@ceph-node01 keepalived]# curl http://100.73.18.152/
<?xml version="1.0" encoding="UTF-8"?><ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Owner><ID>anonymous</ID><DisplayName></DisplayName></Owner><Buckets></Buckets></ListAllMyBucketsResult>[root@ceph-node01 keepalived]#
[root@ceph-node01 keepalived]#
[root@ceph-node01 keepalived]# curl http://100.73.18.153/
<?xml version="1.0" encoding="UTF-8"?><ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Owner><ID>anonymous</ID><DisplayName></DisplayName></Owner><Buckets></Buckets></ListAllMyBucketsResult>[root@ceph-node01 keepalived]#
[root@ceph-node01 keepalived]#
[root@ceph-node01 keepalived]#

s3客戶端測試

[root@ceph-node01 ~]# cat /root/.s3cfg
。。。
host_base = 100.73.18.253:80
host_bucket = 100.73.18.253:80/%(bucket)s
。。。
[root@ceph-node01 ~]#

s3 客戶端驗證

[root@ceph-node01 ~]# s3cmd mb s3://test-1
Bucket 's3://test-1/' created
[root@ceph-node01 ~]# s3cmd ls
...
2020-10-19 13:54 s3://test-1
[root@ceph-node01 ~]#

swift客戶端

# 1. 配置修改並應用
[root@ceph-node01 ~]# cat /etc/profile
...
export ST_AUTH=http://100.73.18.253/auth
export ST_USER=ceph-s3-user:swift
export ST_KEY=0M1GdRTvMSU3fToOxEVXrBjItKLBKtu8xhn3DcEE
[root@ceph-node01 ~]# source /etc/profile

# 2. 客戶端使用
[root@ceph-node01 ~]# swift post test-2
[root@ceph-node01 ~]# swift list
。。。
test-1
test-2
[root@ceph-node01 ~]#

高可用驗證

# 1. 模擬ceph-node02 haproxy 故障
[root@ceph-node01 ~]# systemctl stop haproxy
[root@ceph-node01 ~]# tail -f /var/log/messages
Oct 19 10:23:58 ceph-node01 Keepalived_vrrp[89533]: /usr/bin/killall -0 haproxy exited with status 1
Oct 19 10:23:58 ceph-node01 Keepalived_vrrp[89533]: VRRP_Script(haproxy_check) failed
Oct 19 10:23:58 ceph-node01 Keepalived_vrrp[89533]: VRRP_Instance(RADOSGW) Changing effective priority from 100 to 98
Oct 19 10:23:59 ceph-node01 Keepalived_vrrp[89533]: VRRP_Instance(RADOSGW) Received advert with higher priority 99, ours 98
Oct 19 10:23:59 ceph-node01 Keepalived_vrrp[89533]: VRRP_Instance(RADOSGW) Entering BACKUP STATE
Oct 19 10:23:59 ceph-node01 Keepalived_vrrp[89533]: VRRP_Instance(RADOSGW) removing protocol VIPs.
Oct 19 10:23:59 ceph-node01 Keepalived_vrrp[89533]: VRRP_Instance(RADOSGW) removing protocol iptable drop rule
Oct 19 10:24:00 ceph-node01 ntpd[5618]: Deleting interface #9 eth0, 100.73.18.253#123, interface stats: received=0, sent=0, dropped=0, active_time=180 secs
Oct 19 10:24:00 ceph-node01 Keepalived_vrrp[89533]: /usr/bin/killall -0 haproxy exited with status 1
Oct 19 10:24:02 ceph-node01 Keepalived_vrrp[89533]: /usr/bin/killall -0 haproxy exited with status 1
Oct 19 10:24:04 ceph-node01 Keepalived_vrrp[89533]: /usr/bin/killall -0 haproxy exited with status 1
Oct 19 10:24:06 ceph-node01 Keepalived_vrrp[89533]: /usr/bin/killall -0 haproxy exited with status 1
Oct 19 10:24:08 ceph-node01 Keepalived_vrrp[89533]: /usr/bin/killall -0 haproxy exited with status 1
^C
[root@ceph-node01 ~]#

# 2. 登入 ceph-node02 檢視
[root@ceph-node02 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 06:f6:14:00:0a:8d brd ff:ff:ff:ff:ff:ff
    inet 100.73.18.153/24 brd 100.73.18.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 100.73.18.253/24 scope global secondary eth0
       valid_lft forever preferred_lft forever
[root@ceph-node02 ~]# iptables -t filter -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP all -- 0.0.0.0/0 100.73.18.253

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root@ceph-node02 ~]# iptables -t filter -F
[root@ceph-node02 ~]# ping 100.73.18.253
PING 100.73.18.253 (100.73.18.253) 56(84) bytes of data.
64 bytes from 100.73.18.253: icmp_seq=1 ttl=64 time=0.015 ms
^C
--- 100.73.18.253 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.015/0.015/0.015/0.000 ms
[root@ceph-node02 ~]#

禁用新增 Drop 規則

[root@ceph-node01 ~]# cat /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   notification_email {
     [email protected]
     [email protected]
     [email protected]
   }
   notification_email_from [email protected]
   smtp_server 192.168.200.1
   smtp_connect_timeout 30
   router_id LVS_DEVEL
   vrrp_skip_check_adv_addr
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}
。。。
[root@ceph-node01 ~]#

keepalived 啟動後 iptables 會自動新增 Drop 規則，這是因為全域性配置下使用了vrrp_strict 引數，把此引數從全域性中刪除，此引數的作用是嚴格控制 VRRP 協議，不支援單播模式，註釋掉此選項，將不會預設新增DROP規則。

相關推薦

10.Ceph 基礎篇 - RGW 高可用

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485316&idx=1&sn=d3a6be417aa39bb03d3fc8bf61527a2a&chksm=e9fdd270de8a5b66940ffe07e58535acfa88ebb8342d52510eefee8eba3

Spring Cloud第三篇 | 搭建高可用Eureka註冊中心

​ ​本文是Spring Cloud專欄的第三篇文章，瞭解前兩篇文章內容有助於更好的理解後面文章：

1.Ceph 基礎篇 - 儲存基礎及架構介紹

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485232&idx=1&sn=ff0e93b91432a68699e0e00a96602b78&chksm=e9fdd2c4de8a5bd22d4801cf35f78ffd9d7ab95b2a254bc5a4d181d9247

2.Ceph 基礎篇 - 叢集部署及故障排查

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485243&idx=1&sn=e425c31af90c72c75d535e16d71f728b&chksm=e9fdd2cfde8a5bd9423b9b15f69e305fc5fa30c543f941f57c8b456d284

3.Ceph 基礎篇 - RBD 塊儲存使用

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485253&idx=1&sn=24d9b06a3c48ce74b30acf08807a243b&chksm=e9fdd2b1de8a5ba72ab7b221f3484a95f2a977ff7a607413e3a7b92d042

4.Ceph 基礎篇 - 物件儲存使用

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485256&idx=1&sn=39e072156c87c639e0c64236d3c2d25d&chksm=e9fdd2bcde8a5baa1da7583a34d94ba6c7311d1c354ede8b3fec57b61f9

6.Ceph 基礎篇 - CephFS 檔案系統

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485294&idx=1&sn=e9039504a93382a232b9274b49ccb538&chksm=e9fdd29ade8a5b8c4fb19f1c249ab40ac553dd9737c25ff874f43275a86

5.Ceph 基礎篇 - 認證

文章轉載自：https://mp.weixin.qq.com/s?__biz=MzI1MDgwNzQ1MQ==&mid=2247485272&idx=1&sn=4b27c357411be40cf901c431010aeac2&chksm=e9fdd2acde8a5bbaf8950bd5eacc1b6444c8ed7269b3932fcbaf244ee17

跟我學 Spring Cloud | 第七篇：Spring Cloud Config 配置中心高可用和refresh

Springboot: 2.1.6.RELEASE SpringCloud: Greenwich.SR1 如無特殊說明，本系列教程全採用以上版本

利用swagger打造高可用專案檔案——GO篇

你是否也被沒有檔案的專案折磨？你是否也因為專案需要寫檔案而頭疼？你是否也被年久失修的檔案坑害？少年，吃下我這發安利吧！通過部署 Swagger，這些問題都將遠離你，精美、易讀、可測試、時效性高的檔案，不想試試

javascript中10個正則表示式使用介紹基礎篇

在 JavaScript 中，正則表示式通常用於兩個字串方法 : search() 和 replace()。 search() 方法 用於檢索字串中指定的子字串，或檢索與正則表示式相匹配的子字串，並返回子串的起始位置。

【HDFS篇12】HA高可用 --- HDFS-HA叢集配置

保持自己的節奏前進就對了 HDFDS-HA叢集配置 (一)環境準備 修改IP 修改主機名及主機名和IP地址的對映

Hadoop基礎（四十）：HDFS HA 高可用（三）YARN-HA 配置

1 YARN-HA 工作機制 1. 官方文件： http://hadoop.apache.org/docs/r2.7.2/hadoop-yarn/hadoop-yarn-site/ResourceManagerHA.html

(精華)2020年10月6日 高併發高可用 架構冗餘

冗餘是什麼： 單體 單體：是把系統部署到一臺伺服器上，所有的請求業務都由這臺伺服器處理

(精華)2020年10月7日 高併發高可用 非同步架構

同步架構與非同步架構 背景 把智慧系統比喻成KFC營業廳，處理器是視窗和視窗後面的服務員（把一個視窗當作一個核心），指令集是後面排隊的人，視窗是資料吞吐量。 當中午就餐人多的時候，一個視窗肯定忙不過

(精華)2020年10月10日 高併發高可用 資訊自動化

高可用/併發架構帶來部署和運維挑戰 更多的伺服器，更復雜的軟體架構，更多的工作節點…… 更多的釋出,部署，測試和運維挑戰。

(精華)2020年10月10日 高併發高可用 架構安全

常見的高可用/併發場景帶來挑戰 問題：高可用和架構安全的關係 常見的架構安全問題

Redis從入門到高可用，分散式實踐（1）- 基礎介紹

1 資料結構 2 redis 特性 2.1 速度快 2.2 持久化 2.3 多種資料結構 2.4 功能豐富 2.5 主從複製

Centos 7.6基於MariaDB-server-10.2.32-1.el7 版本實現MHA高可用

背景： 該軟體由兩部分組成：MHA Manager（管理節點）和 MHA Node（資料節點）。MHA Manager 可以單獨部署在一臺獨立的機器上管理多個 master-slave 叢集，也可以部署在一臺 slave 節點上。MHA Node 執行在每臺 MyS

Python入門基礎篇 No.10 —— 同一運算子_整數快取問題

技術標籤：# 基礎python程式語言經驗分享程式人生 Python入門基礎篇 No.10 —— 同一運算子_整數快取問題