溫馨提示×
您好，登錄后才能下訂單哦！
點(diǎn)擊 登錄注冊 即表示同意《億速云用戶服務(wù)條款》
您好，登錄后才能下訂單哦！
各位老鐵們，老張與大家又見面了?？吹礁魑辉诓┛屠锩娼o我的留言和訪問量的情況，我很是欣慰，也謝謝大家對(duì)我的認(rèn)可。我寫這些博客，就是想把自己對(duì)于MySQL數(shù)據(jù)庫的一些看法和自己平時(shí)的實(shí)戰(zhàn)經(jīng)驗(yàn)分享出來，我們可以一起探討，共同進(jìn)步。也保證今后只要一有空就更新博文，推出更多的干貨。
我的學(xué)生經(jīng)常對(duì)我說：“張老師，每次我遇到報(bào)錯(cuò)，有時(shí)還是會(huì)百度，但是最煩的是不知道百度哪篇帖子說的是正確的".其實(shí)這些呢，都是因?yàn)樽约哼€沒有對(duì)MySQL數(shù)據(jù)庫核心知識(shí)的不熟悉，和對(duì)技術(shù)掌握的不牢固。平時(shí)下得功夫還是不到位。我們做技術(shù)這個(gè)行業(yè)，還是需要自己給自己加發(fā)條，促使自己每天都要學(xué)習(xí)一些新的知識(shí)。理論配合實(shí)驗(yàn)一起，先要學(xué)會(huì)多問自己幾個(gè)問題，一個(gè)實(shí)驗(yàn)多做幾遍，可能會(huì)得到不同的實(shí)驗(yàn)效果。學(xué)習(xí)知識(shí)要踏實(shí)下來，學(xué)會(huì)多做實(shí)驗(yàn)總結(jié)。我想今后再遇到報(bào)錯(cuò)，可能自己就會(huì)有一個(gè)清晰的解題思路，這個(gè)需要一定時(shí)間的磨練。
也有人經(jīng)常問Oracle和MySQL到底有啥區(qū)別，其實(shí)MySQL數(shù)據(jù)庫上手很簡單，難的是后期架構(gòu)的設(shè)計(jì)與維護(hù)。老張三部曲中第一部曲MHA希望對(duì)大家在線上部署方面有幫助。
今兒給大家介紹第二部曲，MM+keepalived的環(huán)境部署，我們會(huì)多種數(shù)據(jù)庫的架構(gòu)就可以靈活應(yīng)用到我們的公司。根據(jù)公司業(yè)務(wù)的不同，選擇合適的集群架構(gòu)。
獨(dú)家新課程上線>>MySQL體系結(jié)構(gòu)深入剖析及實(shí)戰(zhàn)DBA視頻課程
MM+keepalived
簡介：
雙主配合keepalived這種架構(gòu)設(shè)計(jì)，也是基于主從復(fù)制的原理而搭建的。
使用MySQL主主復(fù)制技術(shù)+Keepalived是一種簡單、便捷的解決方案，在高可用集群環(huán)境中，keepalived使用VIP，使用Keepalived自帶的服務(wù)監(jiān)控功能和自定義腳本來實(shí)現(xiàn)MySQL故障時(shí)自動(dòng)切換，非常靈活。
應(yīng)用范圍：
一般中小型公司都使用這種架構(gòu)，搭建比較方便簡單；
可以采用主從或者主主模式，在 master 節(jié)點(diǎn)發(fā)生故障后，利用 keepalived 高可用機(jī)制實(shí)現(xiàn)快速切換到 slave 節(jié)點(diǎn)。原來的從庫變成新的主庫。
個(gè)人建議：
一定要完善好切換腳本，keepalived 的切換機(jī)制要合理，避免切換不成功的現(xiàn)象發(fā)生。
從庫的配置盡快要與主庫一致，不能太次；避免主庫宕機(jī)發(fā)生切換，新的主庫（原來的從庫）影響線上業(yè)務(wù)進(jìn)行。
對(duì)于延遲的問題，在這套架構(gòu)中，也不能避免。可以使用 mysql 5.7 中增強(qiáng)半同步完成。也可以改變架構(gòu)使用 PXC，完成時(shí)時(shí)同步功能，基本上沒有延遲；
keepalived 無法解決腦裂的問題，因此在進(jìn)行服務(wù)異常判斷時(shí)，可以修改我們的判斷腳本，通過對(duì)第三方節(jié)點(diǎn)補(bǔ)充檢測來決定是否進(jìn)行切換，可降低腦裂問題產(chǎn)生的風(fēng)險(xiǎn)。
采用 keepalived 這個(gè)架構(gòu)，在設(shè)置兩節(jié)點(diǎn)狀態(tài)時(shí)，都要設(shè)置成不搶占模式，都是 backup 狀態(tài)，通過優(yōu)先級(jí)，來決定誰是主庫。避免腦裂，沖突現(xiàn)象發(fā)生。
安裝好 mysql 需要的一些依賴包；建議配置好 yum 源，用 yum 安裝 keepalived 即可。
搭建架構(gòu)之前理清思路：
首先需要裝有兩臺(tái)mysql的數(shù)據(jù)庫服務(wù)器，兩者之間互為主從模式，都可讀寫。其實(shí)就只有一臺(tái)服務(wù)器A負(fù)責(zé)數(shù)據(jù)的寫入工作，而另一臺(tái)服務(wù)器B作為我們的備用數(shù)據(jù)庫；
安裝keepalived的軟件包，個(gè)人建議使用yum安裝就可以，很方便。當(dāng)然我們要知道yum安裝之后的軟件路徑在什么位置。
整理好keepalived的配置文件，理清keepalived的三種狀態(tài)信息。還要準(zhǔn)備一個(gè)監(jiān)控MySQL的腳本，便于檢測到宕機(jī)順利發(fā)生切換的過程。
所有提供服務(wù)的從服務(wù)器與備用服務(wù)器B進(jìn)行主從同步。----雙主從庫模式
在兩臺(tái)服務(wù)器A和B，當(dāng)配置keepalived的參數(shù)文件中，要注意兩臺(tái)機(jī)器都要采用backup這種狀態(tài)，就是nopreempt這種非搶占模式，避免出現(xiàn)沖突，發(fā)生腦裂現(xiàn)象。
架構(gòu)圖展示：
實(shí)驗(yàn)部署環(huán)境介紹：
192.168.56.100 主 ---master1
192.168.56.101 備庫---master2
都是干凈環(huán)境沒有任何數(shù)據(jù)
VIP：192.168.56.111
MySQL數(shù)據(jù)庫版本5.7.14，采用GTID模式搭建主從環(huán)境
注意事項(xiàng)：
兩臺(tái)機(jī)器的防火墻必須是關(guān)閉狀態(tài)。
兩臺(tái)MySQL數(shù)據(jù)庫配置文件中server-id絕對(duì)不能一樣，要不會(huì)報(bào)1593這個(gè)主從同步的錯(cuò)誤，導(dǎo)致搭建不成功。
實(shí)戰(zhàn)開始：
首先先要搭建兩臺(tái)MySQL數(shù)據(jù)庫為互為主從的架構(gòu)模式。
添加主從同步賬號(hào)：
在192.168.56.100：
grant replication slave on *.* to 'bak'@'192.168.56.%' identified by '123456';
flush privileges;
在192.168.56.101：
grant replication slave on *.* to 'bak'@'192.168.56.%' identified by '123456';
flush privileges;
配置同步信息：
先在192.168.56.101上：
CHANGE MASTER TO MASTER_HOST='192.168.56.100',MASTER_USER='bak',MASTER_PASSWORD='123456',master_auto_position=1;
打開主從同步開關(guān)：
start slave；
查看主從同步狀態(tài)：
root@db 10:49: [(none)]> show slave status\G; *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.56.100 Master_User: bak Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mybinlog.000005 Read_Master_Log_Pos: 234 Relay_Log_File: node2-relay-bin.000010 Relay_Log_Pos: 365 Relay_Master_Log_File: mybinlog.000005 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 234 Relay_Log_Space: 572 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 0 Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 0 Last_IO_Error: Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 3306100 Master_UUID: 913cc1d6-771a-11e7-8fe1-080027f1fd08 Master_Info_File: mysql.slave_master_info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates Master_Retry_Count: 86400 Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: 5a668126-771d-11e7-b14c-08002783b39d:1-2, 913cc1d6-771a-11e7-8fe1-080027f1fd08:1-13 Auto_Position: 1 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)
從庫兩個(gè)工作的線程：IO，SQL都為yes，代表同步搭建成功 Slave_IO_Running: Yes Slave_SQL_Running: Yes
再在192.168.56.100上：
配置主從同步信息：
CHANGE MASTER TO MASTER_HOST='192.168.56.101',MASTER_USER='bak',MASTER_PASSWORD='123456',master_auto_position=1;
開啟主從開關(guān)：
start slave；
查看主從同步狀態(tài)：
root@db 10:49: [(none)]> show slave status\G; *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.56.101 Master_User: bak Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mybinlog.000005 Read_Master_Log_Pos: 234 Relay_Log_File: node1-relay-bin.000008 Relay_Log_Pos: 365 Relay_Master_Log_File: mybinlog.000005 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 234 Relay_Log_Space: 572 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 0 Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 0 Last_IO_Error: Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 3306101 Master_UUID: 5a668126-771d-11e7-b14c-08002783b39d Master_Info_File: mysql.slave_master_info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates Master_Retry_Count: 86400 Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: 5a668126-771d-11e7-b14c-08002783b39d:1-2, 913cc1d6-771a-11e7-8fe1-080027f1fd08:1-13 Auto_Position: 1 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)
同理 Slave_IO_Running: Yes Slave_SQL_Running: Yes 從庫兩個(gè)工作的線程：IO，SQL都為yes，代表同步搭建成功。
分別兩臺(tái)機(jī)器上安裝keepalived的軟件包，可以使用yum安裝方式
yum -y install keepalived;
Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * c6-media: file:///media/CentOS/repodata/repomd.xml: [Errno 14] Could not open/read file:///media/CentOS/repodata/repomd.xml Trying other mirror. file:///media/cdrecorder/repodata/repomd.xml: [Errno 14] Could not open/read file:///media/cdrecorder/repodata/repomd.xml Trying other mirror. c6-media | 4.0 kB 00:00 ... Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package keepalived.x86_64 0:1.2.7-3.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ====================================================================================================================================== Package Arch Version Repository Size ====================================================================================================================================== Installing: keepalived x86_64 1.2.7-3.el6 c6-media 174 k Transaction Summary ====================================================================================================================================== Install 1 Package(s) Total download size: 174 k Installed size: 526 k Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : keepalived-1.2.7-3.el6.x86_64 1/1 Verifying : keepalived-1.2.7-3.el6.x86_64 1/1 Installed: keepalived.x86_64 0:1.2.7-3.el6 Complete!
證明keepalived軟件已經(jīng)存在：
rpm -qa|grep keepalived keepalived-1.2.7-3.el6.x86_64
在兩臺(tái)機(jī)器上分別配置檢測MySQL數(shù)據(jù)庫的腳本：
首先進(jìn)入到y(tǒng)um安裝后的軟件目錄下：
cd /etc/keepalived vim check_mysql.py
腳本通過查看MySQL進(jìn)程的存在，和是否可以連接，來判斷MySQL的狀態(tài)
（這里只展現(xiàn)了腳本中判斷的一部分）
def existMySQL(self): cmd="ps -ef | egrep -i \"mysqld\" | grep %s | egrep -iv \"mysqld_safe\" | grep -v grep | wc -l" % self.dbport mysqldNum = os.popen(cmd).read() cmd ="netstat -tunlp | grep \":%s\" | wc -l" % self.dbport mysqlPortNum= os.popen(cmd).read() #print mysqldNum, mysqlPortNum if ( int(mysqldNum) <= 0): print "error" return 1 if ( int(mysqldNum) > 0 and mysqlPortNum <= 0): return 1 return 0 def connect(self): # print "in db conn" # print "host : %s, port: %d, user: %s, password: %s" % (self.dbhost, self.dbport, self.dbuser, self.dbpassword) try: self.conn=MySQLdb.connect(host="%s"%self.dbhost, port=self.dbport,user="%s"%dbuser, passwd="%s"%self.dbpassword) except Exception, e: # print " Error" print e return 1 return 0 def disconnect(self): if (self.conn): self.conn.close() self.conn = None
在兩臺(tái)機(jī)器上修改keepalived的配置文件：
192.168.56.100上面
vim /etc/keepalived/keepalived.conf
vrrp_instance VI_100 {
state BACKUP
nopreempt
interface eth0
virtual_router_id 100
priority 100
advert_int 5
authentication {
auth_type PASS
auth_pass 1111
}
track_script {
vs_mysql_100
}
virtual_ipaddress {
192.168.56.111
}
}192.168.56.101上面：
vrrp_instance VI_101 {
state BACKUP
nopreempt
interface eth0
virtual_router_id 100
priority 90
advert_int 5
authentication {
auth_type PASS
auth_pass 1111
}
track_script {
vs_mysql_101
}
virtual_ipaddress {
192.168.56.111
}
}總結(jié)：可以看到兩臺(tái)機(jī)器的state都是backup并且都是非搶占模式nopreempt，通過優(yōu)先級(jí)的高低來決定誰是主庫。（這里192.168.56.100是主）還有注意virtual_router_id(虛擬路由id）要保持一致。
接下來可以啟動(dòng)兩臺(tái)機(jī)器的keepalived進(jìn)程：
192.168.56.100：
[root@node1 keepalived]# /etc/init.d/keepalived start Starting keepalived: [ OK ]
觀察日志中信息的變化：
cat /var/log/messages
Aug 3 10:52:17 node1 Keepalived_vrrp[6760]: Opening file '/etc/keepalived/keepalived.conf'. Aug 3 10:52:17 node1 Keepalived_vrrp[6760]: Configuration is using : 62711 Bytes Aug 3 10:52:17 node1 Keepalived_vrrp[6760]: Using LinkWatch kernel netlink reflector... Aug 3 10:52:17 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Entering BACKUP STATE Aug 3 10:52:17 node1 Keepalived_vrrp[6760]: VRRP sockpool: [ifindex(2), proto(112), fd(11,12)] Aug 3 10:52:17 node1 Keepalived_healthcheckers[6759]: Opening file '/etc/keepalived/keepalived.conf'. Aug 3 10:52:17 node1 Keepalived_healthcheckers[6759]: Configuration is using : 4431 Bytes Aug 3 10:52:17 node1 Keepalived_healthcheckers[6759]: Using LinkWatch kernel netlink reflector... Aug 3 10:52:18 node1 Keepalived_vrrp[6760]: VRRP_Script(vs_mysql_100) succeeded Aug 3 10:52:33 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Transition to MASTER STATE Aug 3 10:52:38 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Entering MASTER STATE Aug 3 10:52:38 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) setting protocol VIPs. Aug 3 10:52:38 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Sending gratuitous ARPs on eth0 for 192.168.56.111 Aug 3 10:52:38 node1 Keepalived_healthcheckers[6759]: Netlink reflector reports IP 192.168.56.111 added Aug 3 10:52:43 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Sending gratuitous ARPs on eth0 for 192.168.56.111
可以看到它從backup狀態(tài)切換到master的狀態(tài)了，并且發(fā)送了一個(gè)廣播協(xié)議，證明192.168.56.111已經(jīng)在本臺(tái)機(jī)器上面，其他機(jī)器不要再使用了。
[root@node1 keepalived]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:f1:fd:08 brd ff:ff:ff:ff:ff:ff inet 192.168.56.100/24 brd 192.168.56.255 scope global eth0 inet 192.168.56.111/32 scope global eth0 inet6 fe80::a00:27ff:fef1:fd08/64 scope link valid_lft forever preferred_lft forever
192.168.56.101:
[root@node2 ~]# /etc/init.d/keepalived start Starting keepalived: [ OK ]
cat /var/log/messages
Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Interface queue is empty Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Netlink reflector reports IP 192.168.56.101 added Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Netlink reflector reports IP fe80::a00:27ff:fe83:b39d added Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Registering Kernel netlink reflector Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Registering Kernel netlink command channel Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Opening file '/etc/keepalived/keepalived.conf'. Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Configuration is using : 4561 Bytes Aug 3 10:53:28 node2 Keepalived_healthcheckers[8111]: Using LinkWatch kernel netlink reflector... Aug 3 10:53:28 node2 Keepalived_vrrp[8112]: Opening file '/etc/keepalived/keepalived.conf'. Aug 3 10:53:28 node2 Keepalived_vrrp[8112]: Configuration is using : 62577 Bytes Aug 3 10:53:28 node2 Keepalived_vrrp[8112]: Using LinkWatch kernel netlink reflector... Aug 3 10:53:28 node2 Keepalived_vrrp[8112]: VRRP_Instance(VI_101) Entering BACKUP STATE Aug 3 10:53:28 node2 Keepalived_vrrp[8112]: VRRP sockpool: [ifindex(2), proto(112), fd(12,13)] Aug 3 10:53:28 node2 Keepalived_vrrp[8112]: VRRP_Script(vs_mysql_101) succeeded
這臺(tái)服務(wù)器就是正常的backup狀態(tài)，時(shí)刻準(zhǔn)備著接管主庫的服務(wù)。
模擬一下主庫宕機(jī)的故障切換：
主庫192.168.56.100上面執(zhí)行關(guān)閉MySQL服務(wù)操作：
mysqladmin -uroot -proot123 shutdown
這時(shí)再查看一下keepalived日志的情況：
cat /var/log/messages Aug 3 11:04:17 node1 Keepalived_vrrp[6760]: VRRP_Script(vs_mysql_100) failed Aug 3 11:04:18 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Entering FAULT STATE Aug 3 11:04:18 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) removing protocol VIPs. Aug 3 11:04:18 node1 Keepalived_healthcheckers[6759]: Netlink reflector reports IP 192.168.56.111 removed Aug 3 11:04:18 node1 Keepalived_vrrp[6760]: VRRP_Instance(VI_100) Now in FAULT state
已經(jīng)把vip removed了，并且keepalived的狀態(tài)變成了fault
在備庫192.168.56.101上面查看日志：
cat /var/log/messages Aug 3 11:04:29 node2 Keepalived_vrrp[8112]: VRRP_Instance(VI_101) Transition to MASTER STATE Aug 3 11:04:34 node2 Keepalived_vrrp[8112]: VRRP_Instance(VI_101) Entering MASTER STATE Aug 3 11:04:34 node2 Keepalived_vrrp[8112]: VRRP_Instance(VI_101) setting protocol VIPs. Aug 3 11:04:34 node2 Keepalived_vrrp[8112]: VRRP_Instance(VI_101) Sending gratuitous ARPs on eth0 for 192.168.56.111 Aug 3 11:04:34 node2 Keepalived_healthcheckers[8111]: Netlink reflector reports IP 192.168.56.111 added Aug 3 11:04:39 node2 Keepalived_vrrp[8112]: VRRP_Instance(VI_101) Sending gratuitous ARPs on eth0 for 192.168.56.111
備庫已經(jīng)從backup狀態(tài)切換成master狀態(tài)了。并且VIP（192.168.56.111）已經(jīng)切換過來。
查看ip地址：
[root@node2 ~]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:83:b3:9d brd ff:ff:ff:ff:ff:ff inet 192.168.56.101/24 brd 192.168.56.255 scope global eth0 inet 192.168.56.111/32 scope global eth0 inet6 fe80::a00:27ff:fe83:b39d/64 scope link valid_lft forever preferred_lft forever
主備庫切換成功。
實(shí)戰(zhàn)演練過程結(jié)束，希望對(duì)大家學(xué)習(xí)MySQL高可用集群有幫助。
今后我們可能還會(huì)遇到其他的MySQL高可用架構(gòu)，學(xué)習(xí)它的時(shí)候，先不要忙于搭建，要先弄清原理，整理好實(shí)驗(yàn)過程的思路，遇到報(bào)錯(cuò)，一步步地去排查。自己的水平也會(huì)在這個(gè)歷練的過程中，得到提升。
今后我們可以一起討論，在寫博的過程中難免可能會(huì)有一些筆誤，或是想不周全的地方，希望大家諒解。有不對(duì)的地方歡迎各位老鐵指定。（MySQL高可用集群第二部曲完結(jié)）
第一步曲直通車>> 企業(yè)中MySQL主流高可用架構(gòu)實(shí)戰(zhàn)三部曲之MHA
免責(zé)聲明：本站發(fā)布的內(nèi)容（圖片、視頻和文字）以原創(chuàng)、轉(zhuǎn)載和分享為主，文章觀點(diǎn)不代表本網(wǎng)站立場，如果涉及侵權(quán)請(qǐng)聯(lián)系站長郵箱：is@yisu.com進(jìn)行舉報(bào)，并提供相關(guān)證據(jù)，一經(jīng)查實(shí)，將立刻刪除涉嫌侵權(quán)內(nèi)容。
億速云公眾號(hào)
手機(jī)網(wǎng)站二維碼