返回顶部
首页 > 资讯 > 数据库 >Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用
  • 878
分享到

Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用

2024-04-02 19:04:59 878人浏览 八月长安
摘要

小编给大家分享一下Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用,希望大家阅读完这篇文章之后都有所收获,下面让我们一起去探讨吧!1. 基础安装环境  ,采

小编给大家分享一下Mysql5.6.22双向复制+KeepAlived如何配置mysql高可用,希望大家阅读完这篇文章之后都有所收获,下面让我们一起去探讨吧!

1. 基础安装环境  ,采用mysql5.6.22和keepalived-1.2.15版本安装mysql高可用

此处)折叠或打开

  1. [root@xxt01 ~]# groupadd mysql

  2. [root@xxt01 ~]#useradd -g mysql -s /sbin/nologin -d /opt/mysql mysql

2.3  检查 mysql账号

此处

)折叠或打开

  1. [root@xxt01 ~]#mkdir -p /usr/local/mysql

  2. [root@xxt01 ~]#mkdir -p /usr/local/mysql/data

 2.4.1 执行cmake:       

此处

)折叠或打开

  1. mysql> show master status;

  2. +---------------------+----------+--------------+------------------+-------------------+

  3. | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

  4. +---------------------+----------+--------------+------------------+-------------------+

  5. | mysql-binlog.000002 | 624556 | | | |

  6. +---------------------+----------+--------------+------------------+-------------------+

  7. 1 row in set (0.00 sec)


  8. mysql>

    master 同步操作,参数Slave_IO_Running和Slave_SQL_Running为YES时表示成功,同时无其他错误

点击(此处)折叠或打开

  1. mysql> grant replication slave on *.* to 'slave'@'10.6.0.203' identified by '123456';

  2. Query OK, 0 rows affected (0.00 sec)


  3. mysql>  flush privileges;

  4. Query OK, 0 rows affected (0.00 sec)


  5. mysql> change master to master_host='10.6.0.204',master_user='slave',master_passWord='123456',master_log_file='mysql-binlog.000002',master_log_pos=624556;

  6. Query OK, 0 rows affected, 2 warnings (0.01 sec)


  7. mysql> start slave;

  8. Query OK, 0 rows affected (0.01 sec)

  9. mysql> show slave status\G;
    *************************** 1. row ***************************
                   Slave_IO_State: Waiting for master to send event
                      Master_Host: 10.6.0.204
                      Master_User: slave
                      Master_Port: 3306
                    Connect_Retry: 60
                  Master_Log_File: mysql-binlog.000002
              Read_Master_Log_Pos: 624556
                   Relay_Log_File: xxt01-relay-bin.000002
                    Relay_Log_Pos: 286
            Relay_Master_Log_File: mysql-binlog.000002
                 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: 624556
                  Relay_Log_Space: 459
                  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: 2
                      Master_UUID: aa208c56-216f-11e6-ace3-000c29065661
                 Master_Info_File: /usr/local/mysql/data/master.info
                        SQL_Delay: 0
              SQL_Remaining_Delay: NULL
          Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
               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: 
                    Auto_Position: 0
    1 row in set (0.00 sec)


4.配置keepalived ,实现主从自动切换 
    原理:keepalived用来解决单点故障,提供vrrp(虚拟路由冗余协议)以及healthcheck功能,提供一个vip虚拟ip;
    keepalived的作用是检测服务器的状态,当其中一台服务器出现问题,则将它从组中剔除,恢复后再将它加进来

    服务安装,同时保持master和slave服务配置相同。

点击(此处)折叠或打开

  1. [root@xxt01 ~]# tar zxf keepalived-1.2.15.tar.gz

  2. [root@xxt01 keepalived-1.2.15]# ./configure --prefix=/usr/local/keepalived

  3. [root@xxt01 keepalived-1.2.15]# make && make install

  4. [root@xxt01 etc]# cp -a /usr/local/keepalived/etc/rc.d/init.d/keepalived  /etc/init.d/

  5. [root@xxt01 etc]# cp -a /usr/local/keepalived/etc/sysconfig/keepalived /etc/sysconfig/

  6. [root@xxt01 etc]#   mkdir /etc/keepalived/

  7. [root@xxt01 etc]# cp -a /usr/local/keepalived/etc/keepalived/keepalived.conf /etc/keepalived/

  8. [root@xxt01 etc]# cp -a /usr/local/keepalived/sbin/keepalived /usr/sbin/

4.1 修改203的 /etc/keepalived/keepalived.conf 文件

点击(此处)折叠或打开

  1. ! Configuration File for keepalived


  2. global_defs {

  3. notification_email {

  4. acassen@firewall.loc

  5. failover@firewall.loc

  6. sysadmin@firewall.loc

  7. }

  8. notification_email_from Alexandre.Cassen@firewall.loc

  9. smtp_server 192.168.200.1

  10. smtp_connect_timeout 30

  11. router_id LVS_DEVEL

  12. }


  13. vrrp_instance VI_1 {

  14. state MASTER

  15. interface eth0

  16. virtual_router_id 51

  17. priority 100

  18. advert_int 1

  19. authentication {

  20. auth_type PASS

  21. auth_pass 1111

  22. }

  23. virtual_ipaddress {

  24. 10.6.0.205

  25. }

  26. }


  27. # set mysqld

  28. virtual_server 10.6.0.205 3306 {

  29. delay_loop 6

  30. lb_alGo wrr

  31. lb_kind DR

  32. persistence_timeout 50

  33. protocol tcp


  34. real_server 10.6.0.203 3306 {

  35. weight 3

  36. notify_down /etc/keepalived/killkeepalived.sh

  37. TCP_CHECK {

  38. connect_timeout 10

  39. nb_get_retry 3

  40. delay_before_retry 3

  41. connect_port 3306

  42. }

  43. }

  44. }

4.2配置 killkeepalived.sh

点击(此处)折叠或打开

  1. [root@xxt01 etc]# vi /etc/keepalived/killkeepalived.sh

  2. #!/bin/sh

  3. pkill keepalived

4.3 分别检查mater和slave的 /var/log/message日志,分别做启停mysqld服务测试,信息如下表示服务正常。

点击(此处)折叠或打开

  1. 203 master 服务器

  2. May 24 15:47:38 xxt01 Keepalived_vrrp[14242]: Configuration is using : 63545 Bytes

  3. May 24 15:47:38 xxt01 Keepalived_vrrp[14242]: Using LinkWatch kernel netlink reflector...

  4. May 24 15:47:38 xxt01 Keepalived_vrrp[14242]: VRRP sockpool: [ifindex(2), proto(112), unicast(0), fd(10,11)]

  5. May 24 15:47:38 xxt01 Keepalived_healthcheckers[14241]: Using LinkWatch kernel netlink reflector...

  6. May 24 15:47:38 xxt01 Keepalived_healthcheckers[14241]: Activating healthchecker for service [10.6.0.203]:3306

  7. May 24 15:47:39 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Transition to MASTER STATE

  8. May 24 15:47:40 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Entering MASTER STATE

  9. May 24 15:47:40 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) setting protocol VIPs.

  10. May 24 15:47:40 xxt01 Keepalived_healthcheckers[14241]: Netlink reflector reports IP 10.6.0.205 added

  11. May 24 15:47:40 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.6.0.205

  12. May 24 15:47:45 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.6.0.205

  13. May 24 15:56:27 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Received higher prio advert

  14. May 24 15:56:27 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Entering BACKUP STATE

  15. May 24 15:56:27 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) removing protocol VIPs.

  16. May 24 15:56:27 xxt01 Keepalived_healthcheckers[14241]: Netlink reflector reports IP 10.6.0.205 removed

  17. May 24 16:01:28 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Transition to MASTER STATE

  18. May 24 16:01:29 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Entering MASTER STATE

  19. May 24 16:01:29 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) setting protocol VIPs.

  20. May 24 16:01:29 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.6.0.205

  21. May 24 16:01:29 xxt01 Keepalived_healthcheckers[14241]: Netlink reflector reports IP 10.6.0.205 added

  22. May 24 16:01:34 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.6.0.205

  23. May 24 16:08:36 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Received higher prio advert

  24. May 24 16:08:36 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) Entering BACKUP STATE

  25. May 24 16:08:36 xxt01 Keepalived_vrrp[14242]: VRRP_Instance(VI_1) removing protocol VIPs.

  26. May 24 16:08:36 xxt01 Keepalived_healthcheckers[14241]: Netlink reflector reports IP 10.6.0.205 removed


  27. 204 slave 服务器

  28. May 24 16:08:36 xxt02 Keepalived[15014]: Starting Keepalived v1.2.15 (05/24,2016)

  29. May 24 16:08:36 xxt02 Keepalived[15015]: Starting Healthcheck child process, pid=15016

  30. May 24 16:08:36 xxt02 Keepalived[15015]: Starting VRRP child process, pid=15017

  31. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Netlink reflector reports IP 10.6.0.204 added

  32. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Netlink reflector reports IP fe80::20c:29ff:fe06:5661 added

  33. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: ReGIStering Kernel netlink reflector

  34. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Registering Kernel netlink command channel

  35. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Netlink reflector reports IP 10.6.0.204 added

  36. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Netlink reflector reports IP fe80::20c:29ff:fe06:5661 added

  37. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Registering Kernel netlink reflector

  38. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Opening file '/etc/keepalived/keepalived.conf'.

  39. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Registering Kernel netlink command channel

  40. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Configuration is using : 11978 Bytes

  41. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Registering gratuitous ARP shared channel

  42. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Opening file '/etc/keepalived/keepalived.conf'.

  43. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Configuration is using : 63545 Bytes

  44. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: Using LinkWatch kernel netlink reflector...

  45. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Using LinkWatch kernel netlink reflector...

  46. May 24 16:08:36 xxt02 Keepalived_healthcheckers[15016]: Activating healthchecker for service [10.6.0.204]:3306

  47. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: VRRP sockpool: [ifindex(2), proto(112), unicast(0), fd(10,11)]

  48. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: VRRP_Instance(VI_1) Transition to MASTER STATE

  49. May 24 16:08:36 xxt02 Keepalived_vrrp[15017]: VRRP_Instance(VI_1) Received lower prio advert, forcing new election

  50. May 24 16:08:37 xxt02 Keepalived_vrrp[15017]: VRRP_Instance(VI_1) Entering MASTER STATE

  51. May 24 16:08:37 xxt02 Keepalived_vrrp[15017]: VRRP_Instance(VI_1) setting protocol VIPs.

  52. May 24 16:08:37 xxt02 Keepalived_healthcheckers[15016]: Netlink reflector reports IP 10.6.0.205 added

  53. May 24 16:08:37 xxt02 Keepalived_vrrp[15017]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.6.0.205

  54. May 24 16:08:42 xxt02 Keepalived_vrrp[15017]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.6.0.205

  55. May 24 16:10:14 xxt02 yum[15023]: Installed: 2:nmap-5.51-3.el6.x86_64

4.4 检查服务

点击(此处)折叠或打开

  1. [root@xxt01 mysql]# nmap 10.6.0.205


  2. Starting Nmap 5.51 ( Http://nmap.org ) at 2016-05-24 16:14 CST

  3. mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers

  4. Nmap scan report for 10.6.0.205

  5. Host is up (0.00029s latency).

  6. Not shown: 998 closed ports

  7. PORT     STATE SERVICE

  8. 111/tcp  open  rpcbind

  9. 3306/tcp open  mysql

  10. Mac Address: 00:0C:29:06:56:61 (VMware)


  11. Nmap done: 1 IP address (1 host up) scanned in 1.21 seconds

  12. [root@xxt01 mysql]# nmap 10.6.0.203


  13. Starting Nmap 5.51 ( http://nmap.org ) at 2016-05-24 16:15 CST

  14. mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers

  15. Nmap scan report for 10.6.0.203

  16. Host is up (0.0000050s latency).

  17. Not shown: 998 closed ports

  18. PORT     STATE SERVICE

  19. 111/tcp  open  rpcbind

  20. 3306/tcp open  mysql


  21. Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds

  22. [root@xxt01 mysql]#



  23. [root@xxt01 mysql]# nmap 10.6.0.205


  24. Starting Nmap 5.51 ( http://nmap.org ) at 2016-05-24 16:14 CST

  25. mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers

  26. Nmap scan report for 10.6.0.205

  27. Host is up (0.00029s latency).

  28. Not shown: 998 closed ports

  29. PORT     STATE SERVICE

  30. 111/tcp  open  rpcbind

  31. 3306/tcp open  mysql

  32. MAC Address: 00:0C:29:06:56:61 (VMware)


  33. Nmap done: 1 IP address (1 host up) scanned in 1.21 seconds

  34. [root@xxt01 mysql]# nmap 10.6.0.203


  35. Starting Nmap 5.51 ( http://nmap.org ) at 2016-05-24 16:15 CST

  36. mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers

  37. Nmap scan report for 10.6.0.203

  38. Host is up (0.0000050s latency).

  39. Not shown: 998 closed ports

  40. PORT     STATE SERVICE

  41. 111/tcp  open  rpcbind

  42. 3306/tcp open  mysql


  43. Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds

  44. [root@xxt01 mysql]#

看完了这篇文章,相信你对“Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用”有了一定的了解,如果想了解更多相关知识,欢迎关注编程网数据库频道,感谢各位的阅读!

您可能感兴趣的文档:

--结束END--

本文标题: Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用

本文链接: https://lsjlt.com/news/63254.html(转载时请注明来源链接)

有问题或投稿请发送至: 邮箱/279061341@qq.com    QQ/279061341

猜你喜欢
  • Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用
    小编给大家分享一下Mysql5.6.22双向复制+KeepAlived如何配置mysql的高可用,希望大家阅读完这篇文章之后都有所收获,下面让我们一起去探讨吧!1. 基础安装环境  ,采...
    99+
    2024-04-02
  • Keepalived+MariaDB10配置+双主+高可用数据库
    Keepalived+MariaDB10配置双主高可用数据库  OSRS子网掩码路由网关Centos6.6MariaDB10Keepalived Eth0:192.168.26...
    99+
    2024-04-02
  • Keepalived+Mysql如何配置主主复制
    小编给大家分享一下Keepalived+Mysql如何配置主主复制,相信大部分人都还不怎么了解,因此分享这篇文章给大家参考一下,希望大家阅读完这篇文章后大有收获,下面让我们一起去了解一下吧!安装环境:Hos...
    99+
    2024-04-02
  • Mysql - 配置Mysql主从复制-keepalived高可用-读写分离集群
    目录 高可用: 为什么需要高可用呢? 高可用的主要作用: keepalived是什么?它用在哪里? 什么是VRRP协议,它的作用是什么? 搭建一个基于keepalived的高可用Mysql主从复制读写分离集群 一、项目中的IP地址配置表:...
    99+
    2023-09-18
    数据库
  • mysql+keepalived高可用业务配置教程
    本文主要给大家简单讲讲mysql+keepalived高可用业务配置教程,相关专业术语大家可以上网查查或者找一些相关书籍补充一下,这里就不涉猎了,我们就直奔主题吧,希望mysql+keepalived高可用...
    99+
    2024-04-02
  • MySQL数据库如何配置Keepalived双主
    下面一起来了解下MySQL数据库如何配置Keepalived双主,相信大家看完肯定会受益匪浅,文字在精不在多,希望MySQL数据库如何配置Keepalived双主这篇短内容是你想要的。1、环境设置10.0....
    99+
    2024-04-02
  • MySQL数据库--主主复制+keepalived高可用
                  MySQL数据库--主主复制+keepalived高可用之前我们有学习过mysql的主从复制,主要...
    99+
    2024-04-02
  • keepalived+vip+mysql双机高可用的示例分析
    这篇文章主要为大家展示了“keepalived+vip+mysql双机高可用的示例分析”,内容简而易懂,条理清晰,希望能够帮助大家解决疑惑,下面让小编带领大家一起研究并学习一下“keepalived+vip...
    99+
    2024-04-02
  • mysql如何实现双主复制配置
    这篇文章主要介绍了mysql如何实现双主复制配置,具有一定借鉴价值,感兴趣的朋友可以参考下,希望大家阅读完这篇文章之后大有收获,下面让小编带着大家一起了解一下。  两台...
    99+
    2024-04-02
  • MySQL主主复制+Keepalived打造高可用MySQL集群的步骤
    这篇文章主要介绍“MySQL主主复制+Keepalived打造高可用MySQL集群的步骤”,在日常操作中,相信很多人在MySQL主主复制+Keepalived打造高可用MySQL集群的步骤问题上存在疑惑,小...
    99+
    2024-04-02
  • MySQL主从复制项目(MHA+双主Keepalived)_MySQL高可用复制与分布式集群架构04
    MySQL主从复制项目(MHA+双主Keepalived)_MySQL高可用复制与分布式集群架构04视频教程学习地址    http://edu.51cto.com/cours...
    99+
    2024-04-02
  • 如何搭建keepalived+nginx+httpd+dns高可用双主反向代理服务器
    如何搭建keepalived+nginx+httpd+dns高可用双主反向代理服务器,相信很多没有经验的人对此束手无策,为此本文总结了问题出现的原因和解决方法,通过这篇文章希望你能解决这个问题。rs服务器安装httpd,ip为:192.16...
    99+
    2023-06-05
  • Ubuntu搭建Mysql+Keepalived高可用的实现(双主热备)
    Mysql5.5双机热备 实现方案 安装两台Mysql 安装Mysql5.5 sudo apt-get update apt-get install aptitud...
    99+
    2024-04-02
  • MySQL如何实现双向复制备忘
    这篇文章主要介绍了MySQL如何实现双向复制备忘,具有一定借鉴价值,感兴趣的朋友可以参考下,希望大家阅读完这篇文章之后大有收获,下面让小编带着大家一起了解一下。所谓双向复制实际上至分别配置主从复制。假设有两...
    99+
    2024-04-02
  • MySQL5.7+MHA+Keepalived高可用配置的示例分析
    这篇文章主要介绍了MySQL5.7+MHA+Keepalived高可用配置的示例分析,具有一定借鉴价值,感兴趣的朋友可以参考下,希望大家阅读完这篇文章之后大有收获,下面让小编带着大家一起了解一下。数据库架构...
    99+
    2024-04-02
  • 如何搭建Heartbeat+DRBD+Mysql+Lvs+Keepalived高可用
    这篇文章主要为大家展示了“如何搭建Heartbeat+DRBD+Mysql+Lvs+Keepalived高可用”,内容简而易懂,条理清晰,希望能够帮助大家解决疑惑,下面让小编带领大家一起研究并学习一下“如何...
    99+
    2024-04-02
  • Ubuntu搭建Mysql+Keepalived高可用如何实现
    这篇文章将为大家详细讲解有关Ubuntu搭建Mysql+Keepalived高可用如何实现,小编觉得挺实用的,因此分享给大家做个参考,希望大家阅读完这篇文章后可以有所收获。Mysql5.5双机热备实现方案安装两台Mysql安装Mysql5....
    99+
    2023-06-21
  • 搭建MySQL双主MM+keepalived高可用架构的具体流程
    下文我给大家简单讲讲关于搭建MySQL双主MM+keepalived高可用架构的具体流程,大家之前了解过相关类似主题内容吗?感兴趣的话就一起来看看这篇文章吧,相信看完搭建MySQL双主MM+keepaliv...
    99+
    2024-04-02
  • 如何配置基于双主DRBD的KVM双节点高可用群集
    这篇文章主要为大家展示了“如何配置基于双主DRBD的KVM双节点高可用群集”,内容简而易懂,条理清晰,希望能够帮助大家解决疑惑,下面让小编带领大家一起研究并学习一下“如何配置基于双主DRBD的KVM双节点高可用群集”这篇文章吧。实验目的:构...
    99+
    2023-06-04
  • mysql主从复制读写分离与高可用配置
    一、说明 前面我们说了mysql的安装配置(并提供一键安装脚本),mysql语句使用以及备份恢复mysql数据;本次要介绍的是mysql的主从复制,读写分离;及高可用MHA;环境如下:master:Cent...
    99+
    2024-04-02
软考高级职称资格查询
编程网,编程工程师的家园,是目前国内优秀的开源技术社区之一,形成了由开源软件库、代码分享、资讯、协作翻译、讨论区和博客等几大频道内容,为IT开发者提供了一个发现、使用、并交流开源技术的平台。
  • 官方手机版

  • 微信公众号

  • 商务合作