- 当前位置：首页 >IT科技 >MySQL主从复制读写分离与高可用配置
MySQL主从复制读写分离与高可用配置
发布时间：2025-11-05 14:04:44 来源：码上建站 作者：人工智能
一、主制读说明
前面我们说了mysql的从复安装配置(并提供一键安装
脚本)，mysql语句使用以及备份恢复mysql数据；本次要介绍的写分是mysql的主从复制，读写分离；及高可用MHA。云服务器提供商离高
环境如下：
master:CentOS7_x64 mysql5.721 172.16.3.175 db1
slave1:CentOS7_x64 mysql5.7.21 172.16.3.235 db2
slave2:CentOS7_x64 mysql5.7.21 172.16.3.235 db3
proxysql/MHA:CentOS7_x64 mysql5.7.21 172.16.3.235 proxysql架构图:
说明:
配置测试时为了方便关闭了防火墙头，可用selinux安全策略；
现实中请开放防火墙策略；myslqdb的配置安装已经有脚本一键安装并配置好；这里就不在重复配置；只对对应的角色贴出对应的配置或安装与之相关的软件；二、主从复制配置
一台主数据库，免费源码下载主制读N从节点；从节点开启两个线程，从复通过Slave_IO_Running线程和主节点上有权限的写分账号从 主数据库节点复制binlog日志到本地，能过Slave_SQL_Running线程在本地执行binlog日志,离高达到主从节点内容同步；
master配置:egrep -v (^$|^#) /usr/local/mysql/etc/my.cnf
复制[mysqld] datadir=/data1/mysqldb socket=/tmp/mysql.sock key_buffer_size = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 query_cache_limit = 1M query_cache_size = 64M query_cache_type = 1 symbolic-links=0 innodb_file_per_table=ON skip_name_resolve=ON server-id = 1 log_bin = /data1/mysqldb/mysql-bin.log [mysqld_safe] log-error=/usr/local/mysql/logs/error.log pid-file=/data1/mysqldb/mysql.pid !includedir /usr/local/mysql/etc/my.cnf.d 1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.20.创建从节点同步账号:
复制mysql > grant replication client,replication slave on *.* torepluser@172.16.3.% identified byreplpass; mysql > flush privileges; mysql >show master logs; +------------------+-----------+ | Log_name | File_size | +------------------+-----------+ | mysql-bin.000001 | 622 | 1.2.3.4.5.6.7.主节点上的binlog日志文件及位置;请记下;从节点第一次同步时需要用;
slave节点:egrep -v (^$|^#) /usr/local/mysql/etc/my.cnf
复制[mysqld] datadir=/data1/mysqldb socket=/data1/mysqldb/mysql.sock key_buffer_size = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 query_cache_limit = 1M query_cache_size = 64M query_cache_type = 1 symbolic-links=0 innodb_file_per_table=ON skip_name_resolve=ON server-id = 11 #从节点标识ID 各从节点均不一样 relay_log = relay-log read_only=ON [mysqld_safe] log-error=/usr/local/mysql/log/error.log pid-file=/var/run/mysql/mysql.pid !includedir /usr/local/mysql/etc/my.cnf.d 1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.20.21.22.23.启动mysq数据库
注意:两台从节点的server-id 值不一样;其他的都一样;因此从节点只展示一个配置文件;
登录数据库并同步数据启动slave两台slave均要同步并启动 复制mysql > CHANGE MASTER TO MASTER_HOST="172.16.3.175",MASTER_USER="repluser",MASTER_PASSWORD="replpass",MASTER_PORT=3306,MASTER_LOG_FILE="mysql-bin.000001",MASTER_LOG_POS=622; mysql > start slave; #启动从节点() #查看从节点状态 mysql > SHOW SLAVE STATUS; 站群服务器- 上一篇：小米妙享电脑安装教程（小米妙享电脑安装步骤详解）
- 下一篇：There are many ways to control brightness. According to this discussion[1] and this wiki page [2], the control method could be divided into these categories: brightness is controlled by vendor specified hotkey. And there is no interface for OS to adjust brightness. brightness could be controlled by ACPI ACPIIt is often possible to adjust the backlight by ACPI. This controls the actual LEDs or cathodes of the screen. When this ACPI option is available, the illumination is controllable using a GUI slider in the Display/Screen system settings or by simple commands on the CLI. Different cards might manage this differently. Check /sys/class/backlight to find out: # ls /sys/class/backlight/intel_backlight The directory contains the following files and folders: actual_brightness brightness max_brightness subsystem/ uevent # cat /sys/class/backlight/acpi_video0/max_brightness # echo 5 >/sys/class/backlight/acpi_video0/brightness acpi_osi=Linux acpi_backlight=vendor acpi_osi=Linux acpi_backlight=legacy 看了这个之后，很显然，问题就在于acpi_backlight=vendor will prefer vendor specific driver (e.g. thinkpad_acpi, sony_acpi, etc.) instead of the ACPI video.ko driver. 本文来源：博客园 作者：浮沉雄鹰
益华科技服务器租用IT资讯网亿华云IT技术网香港云服务器企商汇源码库源码下载编程之道益强科技极客编程全栈开发益强智未来亿华云计算运维纵横智能时代益强数据堂亿华互联亿华科技益强IT技术网亿华灵动益强编程堂技术快报益华IT技术论坛益强前沿资讯码力社IT资讯网码上建站创站工坊极客码头益强科技多维IT资讯益强资讯优选思维库益强编程舍科技前瞻亿华云云站无忧亿华智造
- Copyright © 2025 Powered by MySQL主从复制读写分离与高可用配置,码上建站 滇ICP备2023006006号-47sitemap