惠州做棋牌网站建设哪家公司收费合理,外贸网站建设厦门,qq空间是哪个公司开发的,优化好的网站❤️作者简介#xff1a;2022新星计划第三季云原生与云计算赛道Top5#x1f3c5;、华为云享专家#x1f3c5;、云原生领域潜力新星#x1f3c5; #x1f49b;博客首页#xff1a;C站个人主页#x1f31e; #x1f497;作者目的#xff1a;如有错误请指正#xff0c;将… ❤️作者简介2022新星计划第三季云原生与云计算赛道Top5、华为云享专家、云原生领域潜力新星 博客首页C站个人主页 作者目的如有错误请指正将来会不断的完善笔记帮助更多的Java爱好者入门共同进步 文章目录 分库分表-ShardingSphere 4.x2ShardingSphere概述Sharding-JDBC实战教程下Sharding-JDBC广播表Config实体类ConfigMapper接口application.propertiesjunit测试类测试1往ds1.t_config这个广播表插入数据 Sharding-JDBC读写分离⭐Docker搭建MySQL主从复制1主1从⭐Master主节点配置Slave从节点配置主从同步失败问题Slave_SQL_Running:NoSlave_SQL_Running:No的解决办法 给Master和Slave的MySQL各自插入一张表⭐数据库orderdb1数据库表orderdb1.order 开始配置Sharding-JDBC主从复制和读写分离⭐application.propertiesjunit测试类测试1测试主从同步读写分离写操作⭐测试2测试读写分离读操作⭐ 注意事项遇到的bug的解决方案⭐问题1Druid数据源问题 Sharding-Proxy实战教程Linux下载Sharding-Proxy4.1.1window版本也是一样的安装方式⭐方式1官网下载缺点是需要修改很多地方而且下载很慢不推荐方式2sharding-proxy的改进版优点拿来即用不用修改任何东西下载快。推荐⭐ Linux安装JDK8Sharding-Proxy需要JDK环境⭐Sharding-Proxy基本配置⭐Sharding-Proxy分库分表⭐数据库orderdb1和orderdb2Docker启动一个MySQL并执行上面的命令开始配置分库分表 Sharding-Proxy读写分离⭐Docker搭建MySQL主从复制1主1从⭐Master主节点配置Slave从节点配置主从同步失败问题Slave_SQL_Running:NoSlave_SQL_Running:No的解决办法 给Master和Slave的MySQL各自插入一张表⭐数据库orderdb1数据库表orderdb1.order 开始配置Sharding-Proxy读写分离⭐ 分库分表-ShardingSphere 4.x2
项目所在仓库
ShardingSphere概述
Apache ShardingSphere 是一款开源的分布式数据库生态项目由 JDBC 和 Proxy 两款产品组成。 其核心采用可插拔架构通过组件扩展功能。 对上以数据库协议及 SQL 方式提供诸多增强功能包括数据分片、访问路由、数据安全等对下原生支持 MySQL、PostgreSQL、SQL Server、Oracle 等多种数据存储引擎。 Apache ShardingSphere 项目理念是提供数据库增强计算服务平台进而围绕其上构建生态。 充分利用现有数据库的计算与存储能力通过插件化方式增强其核心能力为企业解决在数字化转型中面临的诸多使用难点为加速数字化应用赋能。
Sharding-JDBC实战教程下
Sharding-JDBC广播表
Config实体类
package com.boot.entity;import com.baomidou.mybatisplus.annotation.TableField;
import com.baomidou.mybatisplus.annotation.TableName;
import lombok.AllArgsConstructor;
import lombok.Data;
import lombok.NoArgsConstructor;
import lombok.experimental.Accessors;import java.io.Serializable;/*** TODO: 2022/8/8* author youzhengjie*///lombok注解简化开发
Data
AllArgsConstructor
NoArgsConstructor
Accessors(chain true) //开启链式编程
TableName(t_config)
public class Config implements Serializable {TableField(config_id)private Long configId;TableField(config_info)private String configInfo;
}ConfigMapper接口
package com.boot.dao;import com.baomidou.mybatisplus.core.mapper.BaseMapper;
import com.boot.entity.Config;
import org.apache.ibatis.annotations.Mapper;
import org.springframework.stereotype.Repository;Mapper
Repository
public interface ConfigMapper extends BaseMapperConfig {}application.properties
#配置ShardingSphere数据源,定义一个或多个数据源名称
spring.shardingsphere.datasource.namesds1,ds2#配置ds1的数据源对应orderdb1数据库
spring.shardingsphere.datasource.ds1.typecom.alibaba.druid.pool.DruidDataSource
spring.shardingsphere.datasource.ds1.driver-class-namecom.mysql.jdbc.Driver
spring.shardingsphere.datasource.ds1.urljdbc:mysql://localhost:3306/orderdb1?useSSLfalseautoReconnecttruecharacterEncodingUTF-8serverTimezoneUTC
spring.shardingsphere.datasource.ds1.usernameroot
spring.shardingsphere.datasource.ds1.password18420163207#配置ds2的数据源对应orderdb2数据库
spring.shardingsphere.datasource.ds2.typecom.alibaba.druid.pool.DruidDataSource
spring.shardingsphere.datasource.ds2.driver-class-namecom.mysql.jdbc.Driver
spring.shardingsphere.datasource.ds2.urljdbc:mysql://localhost:3306/orderdb2?useSSLfalseautoReconnecttruecharacterEncodingUTF-8serverTimezoneUTC
spring.shardingsphere.datasource.ds2.usernameroot
spring.shardingsphere.datasource.ds2.password18420163207# 配置广播表主键生成策略
spring.shardingsphere.sharding.tables.t_config.key-generator.column config_id
spring.shardingsphere.sharding.tables.t_config.key-generator.typeSNOWFLAKE# 配置广播表表名广播表最核心的就是这个上面配置了两个数据源ds1和ds2
# 广播表就是说当我们插入数据到ds1.t_config或者ds2.t_config中的随便那一个另外一个数据源的t_config表也会自动插入相同的数据其他操作都是一样会自动同步
# 广播表会找到spring.shardingsphere.datasource.names配置的数据源列表对所有t_config进行同步。
spring.shardingsphere.sharding.broadcast-tablest_config#开启ShardingSphere的SQL输出日志
spring.shardingsphere.props.sql.showtrue
# 在映射实体或者属性时将数据库中表名和字段名中的下划线去掉按照驼峰命名法映射 order_id --- orderId
mybatis-plus.configuration.map-underscore-to-camel-casetrue# 这个配置一定要加注意
spring.main.allow-bean-definition-overriding truejunit测试类
测试1往ds1.t_config这个广播表插入数据 Autowiredprivate ConfigMapper configMapper; Testvoid addConfigToBroadcastTable(){Config config new Config();config.setConfigInfo(配置信息123);configMapper.insert(config);}输出日志 查看数据库 Sharding-JDBC读写分离⭐
Docker搭建MySQL主从复制1主1从⭐
Master主节点配置
1运行一个mysql容器实例。作为Master节点如果没有mysql镜像则会自动拉取
docker run -p 3307:3306 \
-v /my-sql/mysql-master/log:/var/log/mysql \
-v /my-sql/mysql-master/data:/var/lib/mysql \
-v /my-sql/mysql-master/conf:/etc/mysql \
-e MYSQL_ROOT_PASSWORD123456 \
--name mysql-master \
-d mysql:5.72创建my.cnf文件也就是mysql的配置文件
vim /my-sql/mysql-master/conf/my.cnf将内容粘贴进my.cnf文件
[client]
# 指定编码格式为utf8,默认的MySQL会有中文乱码问题
default_character_setutf8
[mysqld]
collation_serverutf8_general_ci
character_set_serverutf8# 全局唯一id不允许有相同的
server_id200
binlog-ignore-dbmysql
# 指定MySQL二进制日志可以修改
log-binorder-mysql-bin
# binlog最大容量
binlog_cache_size1M
# 二进制日志格式这里指定的是混合日志
binlog_formatmixed
# binlog的有效期单位天
expire_logs_days7
slave_skip_errors10623重启该mysql容器实例
docker restart mysql-master4进入容器内部并登陆mysql密码默认是123456
$ docker exec -it mysql-master /bin/bash
$ mysql -uroot -p5在Master节点的MySQL中创建用户和分配权限
在主数据库创建的该帐号密码只是用来进行同步数据。
create user slave% identified by 123456;grant replication slave, replication client on *.* to slave%;Slave从节点配置
1运行一个MySQL容器实例作为slave节点从节点
docker run -p 3308:3306 \
-v /my-sql/mysql-slave/log:/var/log/mysql \
-v /my-sql/mysql-slave/data:/var/lib/mysql \
-v /my-sql/mysql-slave/conf:/etc/mysql \
-e MYSQL_ROOT_PASSWORD123456 \
--name mysql-slave \
-d mysql:5.72创建my.cnf文件也就是mysql的配置文件
vim /my-sql/mysql-slave/conf/my.cnf将内容粘贴进my.cnf文件
[client]
# 指定编码格式为utf8,默认的MySQL会有中文乱码问题
default_character_setutf8
[mysqld]
collation_serverutf8_general_ci
character_set_serverutf8# 全局唯一id不允许有相同的
server_id201
binlog-ignore-dbmysql
# 指定MySQL二进制日志可以修改
log-binorder-mysql-bin
# binlog最大容量
binlog_cache_size1M
# 二进制日志格式这里指定的是混合日志
binlog_formatmixed
# binlog的有效期单位天
expire_logs_days7
slave_skip_errors1062
# 表示slave将复制事件写进自己的二进制日志
log_slave_updates1
# 表示从机只能读
read_only13重启该mysql容器实例
docker restart mysql-slave4查看容器实例是否都是up
[rootk8s-master ~]# docker ps | grep mysql
3be6e547ab4e mysql:5.7 docker-entrypoint.s… About a minute ago Up 24 seconds 33060/tcp, 0.0.0.0:3308-3306/tcp, :::3308-3306/tcp mysql-slave
214fed096342 mysql:5.7 docker-entrypoint.s… 7 minutes ago Up 4 minutes 33060/tcp, 0.0.0.0:3307-3306/tcp, :::3307-3306/tcp mysql-master5进入从机MySQL
$ docker exec -it mysql-slave /bin/bash
$ mysql -uroot -p6查询Master数据库所在的服务器复制起来
[Master数据库所在的服务器 ~]# ifconfig
ens33: flags4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500inet 192.168.184.100 netmask 255.255.255.0 broadcast 192.168.184.255inet6 fe80::224c:e6cc:c9ab:f4e0 prefixlen 64 scopeid 0x20linkether 00:0c:29:af:f8:9f txqueuelen 1000 (Ethernet)RX packets 113915 bytes 164657385 (157.0 MiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 12073 bytes 970949 (948.1 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 07在从数据库slave配置主从同步记住下面这个命令要在从slave数据库执行
在Master节点中找到ens33的ip地址并放到下面的master_host中记住这个ip是Master数据库所在的服务器ip不是从Slave数据库的ip
change master to master_host192.168.184.100,master_userslave,master_password123456,master_port3307,master_log_fileorder-mysql-bin.000001,master_log_pos617,master_connect_retry30;配置参数解析 master_host主数据库Master的 ip 地址 master_user在Master数据库中创建的用来进行同步的帐号 master_password在Master数据库中创建的用来进行同步的帐号的密码 master_portMaster数据库的 MySQL端口号这里是3307 master_log_fileMySQL的 binlog文件名 master_log_posbinlog读取位置
8在从数据库slave查看主从同步状态
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Master_Host: 192.168.184.100Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 617Relay_Log_File: 3be6e547ab4e-relay-bin.000001Relay_Log_Pos: 4Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: NoSlave_SQL_Running: NoReplicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0Last_Error: Skip_Counter: 0Exec_Master_Log_Pos: 617Relay_Log_Space: 154Until_Condition: NoneUntil_Log_File: Until_Log_Pos: 0Master_SSL_Allowed: NoMaster_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: NoLast_IO_Errno: 0Last_IO_Error: Last_SQL_Errno: 0Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 0Master_UUID: Master_Info_File: /var/lib/mysql/master.infoSQL_Delay: 0SQL_Remaining_Delay: NULLSlave_SQL_Running_State: Master_Retry_Count: 86400Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version:
1 row in set (0.15 sec)ERROR:
No query specified我们找到里面的Slave_IO_Running: NoSlave_SQL_Running: No属性发现都是No的状态证明主从同步还没有开始。。。
9在从数据库slave正式开启主从同步
start slave;10再次在从数据库中查看主从同步状态
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.184.100Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 617Relay_Log_File: 3be6e547ab4e-relay-bin.000002Relay_Log_Pos: 326Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: YesSlave_SQL_Running: YesReplicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0Last_Error: Skip_Counter: 0Exec_Master_Log_Pos: 617Relay_Log_Space: 540Until_Condition: NoneUntil_Log_File: Until_Log_Pos: 0Master_SSL_Allowed: NoMaster_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: NoLast_IO_Errno: 0Last_IO_Error: Last_SQL_Errno: 0Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 200Master_UUID: a606bab7-1736-11ed-9207-0242ac110002Master_Info_File: /var/lib/mysql/master.infoSQL_Delay: 0SQL_Remaining_Delay: NULLSlave_SQL_Running_State: Slave has read all relay log; waiting for more updatesMaster_Retry_Count: 86400Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version:
1 row in set (0.09 sec)ERROR:
No query specified我们可以看到已经都为yes了说明主从同步已经开启。
也可以用Navicat去连接这两个数据库。如果Navicat出现连接不了docker的mysql则可以
方法一关闭防火墙测试环境用生产环境不可以用
sudo systemctl stop firewalld方法二开放防火墙对应端口比如master数据库的3307和slave数据库的3308生产环境用这个
主从同步失败问题Slave_SQL_Running:No
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.184.132Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 3752Relay_Log_File: 2c4136668536-relay-bin.000002Relay_Log_Pos: 326Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: YesSlave_SQL_Running: NoReplicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 1007Last_Error: Error Cant create database mall; database exists on query. Default database: mall. Query: create database mallSlave_SQL_Running为No的状态那么这是为什么呢可以看到Last_Error: Error ‘Can’t create database ‘mall’; database exists’ on query. Default database: ‘mall’. Query: ‘create database mall’原因是主数据库Master和从数据库slave不一致造成的我在从数据库执行了命令导致数据不一致最终导致主从复制失败。
Slave_SQL_Running:No的解决办法
1把主数据库和从数据库变成一模一样也就是把多余的数据库和表删除掉变成默认的mysql状态。切记生产环境下要做好数据备份
2结束同步
stop slave;3再次开启同步
start slave;4搞定
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.184.132Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 3752Relay_Log_File: 2c4136668536-relay-bin.000003Relay_Log_Pos: 326Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: YesSlave_SQL_Running: Yes给Master和Slave的MySQL各自插入一张表⭐
数据库orderdb1
CREATE DATABASE orderdb1;数据库表orderdb1.order
SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS 0;DROP TABLE IF EXISTS order;
CREATE TABLE order (order_id bigint(20) NOT NULL,order_info varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,user_id bigint(20) NOT NULL,PRIMARY KEY (order_id) USING BTREE
) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT DYNAMIC;SET FOREIGN_KEY_CHECKS 1;查看数据库 开始配置Sharding-JDBC主从复制和读写分离⭐
application.properties
#配置ShardingSphere数据源,定义一个或多个数据源名称
spring.shardingsphere.datasource.namesmaster01,slave01#配置master01的数据源对应master主数据库
spring.shardingsphere.datasource.master01.typecom.alibaba.druid.pool.DruidDataSource
spring.shardingsphere.datasource.master01.driver-class-namecom.mysql.jdbc.Driver
spring.shardingsphere.datasource.master01.urljdbc:mysql://192.168.184.100:3307/orderdb1?useSSLfalseautoReconnecttruecharacterEncodingUTF-8serverTimezoneUTC
spring.shardingsphere.datasource.master01.usernameroot
spring.shardingsphere.datasource.master01.password123456#配置slave01的数据源对应slave从数据库
spring.shardingsphere.datasource.slave01.typecom.alibaba.druid.pool.DruidDataSource
spring.shardingsphere.datasource.slave01.driver-class-namecom.mysql.jdbc.Driver
spring.shardingsphere.datasource.slave01.urljdbc:mysql://192.168.184.100:3308/orderdb1?useSSLfalseautoReconnecttruecharacterEncodingUTF-8serverTimezoneUTC
spring.shardingsphere.datasource.slave01.usernameroot
spring.shardingsphere.datasource.slave01.password123456# 配置order表主键生成策略
spring.shardingsphere.sharding.tables.order.key-generator.columnorder_id
spring.shardingsphere.sharding.tables.order.key-generator.typeSNOWFLAKE# 主从复制读写分离三大配置核心# 主从复制数据源定义为master-slave-datasource01其实都可以
# master-data-source-name为上面定义的master主数据源的名称只能写一个主库写操作全部到master01数据源
spring.shardingsphere.sharding.master-slave-rules.master-slave-datasource01.master-data-source-namemaster01
# slave-data-source-names为上面定义的slave从数据源的名称列表**可以写多个用逗号分隔**读操作全部到slave01数据源
spring.shardingsphere.sharding.master-slave-rules.master-slave-datasource01.slave-data-source-namesslave01
# order分表策略固定分配至 master-slave-datasource01 的 order 真实表
spring.shardingsphere.sharding.tables.order.actual-data-nodesmaster-slave-datasource01.order#开启ShardingSphere的SQL输出日志
spring.shardingsphere.props.sql.showtrue
# 在映射实体或者属性时将数据库中表名和字段名中的下划线去掉按照驼峰命名法映射 order_id --- orderId
mybatis-plus.configuration.map-underscore-to-camel-casetrue# 这个配置一定要加注意
spring.main.allow-bean-definition-overriding truejunit测试类
测试1测试主从同步读写分离写操作⭐ Autowiredprivate OrderMapper orderMapper;//测试主从同步读写分离写操作Testvoid addOrder(){Order order new Order();order.setOrderInfo(测试主从复制).setUserId(1001L);orderMapper.insert(order);}输出日志查看写操作是到哪个数据源中执行 查看数据库查看主从复制是否成功 测试2测试读写分离读操作⭐ // 测试读写分离读操作Testvoid selectOrder(){ListOrder orders orderMapper.selectList(null);orders.forEach(System.out::println);}输出日志查看读操作是到哪个数据源中执行 注意事项遇到的bug的解决方案⭐
问题1Druid数据源问题
不要使用druid-spring-boot-starter这个依赖否则启动会出现问题会有冲突。
解决方案使用下面的Druid数据源可以自己调整版本其他不动
!-- 要使用下面这个druid依赖不能使用druid-spring-boot-starter的依赖--dependencygroupIdcom.alibaba/groupIdartifactIddruid/artifactIdversion1.2.6/version/dependencySharding-Proxy实战教程
ShardingSphere-Proxy 是 Apache ShardingSphere 的第二个产品。 它定位为透明化的数据库代理端通过实现数据库二进制协议对异构语言提供支持。 目前提供 MySQL 和 PostgreSQL 协议透明化数据库操作对 DBA 更加友好。
ShardingSphere-Proxy 的优势在于对异构语言的支持以及为 DBA 提供可操作入口。
Linux下载Sharding-Proxy4.1.1window版本也是一样的安装方式⭐
方式1官网下载缺点是需要修改很多地方而且下载很慢不推荐
1进入官网下载
shardingsphere所有版本 2解压Sharding-Proxy包然后把lib目录下的所有文件后缀名都改成.jar这里是一个坑有一些文件后缀名不是.jar此时我们需要更改过来 3下载mysql的jar包放到Sharding-Proxy的lib目录下然后打成zip包上传到服务器
mysql-connector-java-8快速下载地址 4查看sharding-proxy的zip包是否上传成功
[rootk8s-master sharding-proxy]# pwd
/root/sharding-proxy
[rootk8s-master sharding-proxy]# ls
apache-shardingsphere-4.1.1-sharding-proxy-bin.zip5由于这个sharding-proxy是zip包所以要下载unzip进行解压缩。
yum -y install unzip6解压sharding-proxy
unzip apache-shardingsphere-4.1.1-sharding-proxy-bin.zip7给文件夹改个名
mv apache-shardingsphere-4.1.1-sharding-proxy-bin sharding-proxy-4.1.1方式2sharding-proxy的改进版优点拿来即用不用修改任何东西下载快。推荐⭐
下载地址 1将zip包上传到服务器 2查看sharding-proxy的zip包是否上传成功
[rootk8s-master sharding-proxy]# pwd
/root/sharding-proxy
[rootk8s-master sharding-proxy]# ls
apache-shardingsphere-4.1.1-sharding-proxy-bin.zip3由于这个sharding-proxy是zip包所以要下载unzip进行解压缩。
yum -y install unzip4解压sharding-proxy
unzip apache-shardingsphere-4.1.1-sharding-proxy-bin.zip5给文件夹改个名
mv apache-shardingsphere-4.1.1-sharding-proxy-bin sharding-proxy-4.1.1Linux安装JDK8Sharding-Proxy需要JDK环境⭐
1去官网下载JDK8的tar.gz包或者下载我们下面给的地址的zip包。然后上传到Linux服务器我们拿下面的zip包举例
快速下载JDK8的Linux包
[rootk8s-master jdk]# pwd
/root/jdk
[rootk8s-master jdk]# ls
jdk1.8-linux.zip2解压zip包
unzip jdk1.8-linux.zip3在/usr/local下创建文件夹
mkdir -p /usr/local/java4将刚刚解压到的jdk复制过去
cp -rf jdk1.8-linux /usr/local/java5当前jdk目录
[rootk8s-master java]# pwd
/usr/local/java
[rootk8s-master java]# ls
jdk1.8-linux6配置环境变量
在最后一行粘贴注意JAVA_HOME/usr/local/java/jdk1.8-linux 就是你刚刚copy到/usr/local/java下的java目录文件夹
export JAVA_HOME/usr/local/java/jdk1.8-linux
export CLASSPATH.:$JAVA_HOME/jre/lib/rt.jar:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
export PATH$PATH:$JAVA_HOME/bin7让刚刚设置的环境变量生效并检查是否安装成功
source /etc/profile8给/usr/local/java/jdk1.8-linux/bin/java目录权限
chmod x /usr/local/java/jdk1.8-linux/bin/java9查看是否安装成功
[rootk8s-master java]# java -version
java version 1.8.0_333
Java(TM) SE Runtime Environment (build 1.8.0_333-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.333-b02, mixed mode)Sharding-Proxy基本配置⭐
1进入sharding-proxy的配置文件所在目录
cd /root/sharding-proxy/sharding-proxy-4.1.1/conf2删除文件 server.yaml
rm -f /root/sharding-proxy/sharding-proxy-4.1.1/conf/server.yaml3重新编辑server.yaml
vi /root/sharding-proxy/sharding-proxy-4.1.1/conf/server.yaml内容如下
# orchestration配置服务治理例如nacos、zookeeper等等都可以接入进去#orchestration:
# orchestration_ds:
# orchestrationType: registry_center,config_center # 服务治理的类型一般就是注册中心和配置中心
# instanceType: zookeeper #服务治理的类型例如nacos、zookeeper等等
# serverLists: localhost:2181 #服务治理的url地址也就是nacos、zookeeper的地址
# namespace: orchestration
# props:
# overwrite: false
# retryIntervalMilliseconds: 500
# timeToLiveSeconds: 60
# maxRetries: 3
# operationTimeoutMilliseconds: 500# 配置用户帐号密码权限
authentication:users:root: # 这个代表帐号为rootpassword: root # 帐号为root的用户密码为root 并且权限最高sharding: # 这个代表帐号为shardingpassword: sharding # 帐号为sharding的用户密码为shardingauthorizedSchemas: sharding_db # 帐号为sharding的用户只能操作sharding_db数据库# 下面的配置不用管把注释去掉即可。
props:max.connections.size.per.query: 1acceptor.size: 16 # The default value is available processors count * 2.executor.size: 16 # Infinite by default.proxy.frontend.flush.threshold: 128 # The default value is 128.# LOCAL: Proxy will run with LOCAL transaction.# XA: Proxy will run with XA transaction.# BASE: Proxy will run with B.A.S.E transaction.proxy.transaction.type: LOCALproxy.opentracing.enabled: falseproxy.hint.enabled: falsequery.with.cipher.column: truesql.show: falseallow.range.query.with.inline.sharding: falseSharding-Proxy分库分表⭐
数据库orderdb1和orderdb2
CREATE DATABASE orderdb1;
CREATE DATABASE orderdb2;数据库逻辑表orderdb1和orderdb2数据库都要执行下面的语句
SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS 0;DROP TABLE IF EXISTS order;
CREATE TABLE order (order_id bigint(20) NOT NULL,order_info varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,user_id bigint(20) NOT NULL,PRIMARY KEY (order_id) USING BTREE
) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT DYNAMIC;DROP TABLE IF EXISTS order_1;
CREATE TABLE order_1 (order_id bigint(20) NOT NULL,order_info varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,user_id bigint(20) NOT NULL,PRIMARY KEY (order_id) USING BTREE
) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT DYNAMIC;DROP TABLE IF EXISTS order_2;
CREATE TABLE order_2 (order_id bigint(20) NOT NULL,order_info varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,user_id bigint(20) NOT NULL,PRIMARY KEY (order_id) USING BTREE
) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT DYNAMIC;DROP TABLE IF EXISTS t_config;
CREATE TABLE t_config (config_id bigint(20) NOT NULL,config_info text CHARACTER SET utf8 COLLATE utf8_general_ci NULL,PRIMARY KEY (config_id) USING BTREE
) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT Dynamic;SET FOREIGN_KEY_CHECKS 1;Docker启动一个MySQL并执行上面的命令
docker run -p 3311:3306 \
-v /my-sql/mysql01/log:/var/log/mysql \
-v /my-sql/mysql01/data:/var/lib/mysql \
-v /my-sql/mysql01/conf:/etc/mysql \
-e MYSQL_ROOT_PASSWORD123456 \
--name mysql01 \
-d mysql:5.7效果图 开始配置分库分表
1删除 config-sharding.yaml或者直接编辑都可以
rm -f /root/sharding-proxy/sharding-proxy-4.1.1/conf/config-sharding.yaml2重新编辑config-sharding.yaml
vi /root/sharding-proxy/sharding-proxy-4.1.1/conf/config-sharding.yaml内容如下
# sharding-proxy分库分表默认的代理数据库通过这个数据库可以访问我们真实的数据库不用改它
schemaName: sharding_db
# 配置数据源
dataSources:ds1: # 定义一个ds1数据源url: jdbc:mysql://192.168.184.100:3311/orderdb1?serverTimezoneUTCuseSSLfalse #mysql的urlusername: root # mysql帐号password: 123456 # mysql密码connectionTimeoutMilliseconds: 30000idleTimeoutMilliseconds: 60000maxLifetimeMilliseconds: 1800000maxPoolSize: 50ds2: # 定义一个ds2数据源url: jdbc:mysql://192.168.184.100:3311/orderdb2?serverTimezoneUTCuseSSLfalse #mysql的urlusername: root # mysql帐号password: 123456 # mysql密码connectionTimeoutMilliseconds: 30000idleTimeoutMilliseconds: 60000maxLifetimeMilliseconds: 1800000maxPoolSize: 50
#配置分片规则
shardingRule:tables:order: # 逻辑表名我们的逻辑表是orderactualDataNodes: ds${1..2}.order_${1..2} #数据节点分布没有真实表的话sharding-proxy会自动生成所以只需要逻辑表即可databaseStrategy: #分库策略inline: # 指定inline分库策略shardingColumn: order_id #分片键algorithmExpression: ds${order_id % 2 1} # 分片算法 tableStrategy: # 分表策略inline: # 指定inline分表策略shardingColumn: order_id #分片键algorithmExpression: order_${order_id % 2 1} # 分片算法keyGenerator: # 主键生成策略type: SNOWFLAKE #雪花算法column: order_id #主键字段3给sharding-proxy启动脚本权限
[rootk8s-master bin]# cd /root/sharding-proxy/sharding-proxy-4.1.1/bin
[rootk8s-master bin]# chmod ux *.sh4启动 Sharding-Proxy 服务指定sharding-proxy的端口为3366不要使用默认端口
[rootk8s-master bin]# pwd
/root/sharding-proxy/sharding-proxy-4.1.1/bin
[rootk8s-master bin]# ./start.sh 3366
Starting the Sharding-Proxy ...
The port is 3366
The classpath is /root/sharding-proxy/sharding-proxy-4.1.1/conf:.:..:/root/sharding-proxy/sharding-proxy-4.1.1/lib/*:/root/sharding-proxy/sharding-proxy-4.1.1/lib/*:/root/sharding-proxy/sharding-proxy-4.1.1/ext-lib/*
Please check the STDOUT file: /root/sharding-proxy/sharding-proxy-4.1.1/logs/stdout.log5查看是否启动成功
cat /root/sharding-proxy/sharding-proxy-4.1.1/logs/stdout.log6application.properties注意下面的账号、密码、IP、端口、数据库全部要换成sharding-proxy的
#关闭shardingsphere-JDBC由于我们不使用shardingsphere-JDBC所以需要先关闭
spring.shardingsphere.enabledfalse# 配置普通的JDBC数据源去连接sharding-proxy的分库分表代理数据库
spring.datasource.typecom.alibaba.druid.pool.DruidDataSource
spring.datasource.driver-class-namecom.mysql.jdbc.Driver
# 将url换成sharding-proxy代理数据库的IP和端口3366数据库统一换成sharding_dbsharding-proxy的分库分表代理数据库-----重点
spring.datasource.urljdbc:mysql://192.168.184.100:3366/sharding_db?useSSLfalseautoReconnecttruecharacterEncodingUTF-8serverTimezoneUTC
# sharding-proxy的账号
spring.datasource.usernameroot
# sharding-proxy的密码
spring.datasource.passwordroot# 在映射实体或者属性时将数据库中表名和字段名中的下划线去掉按照驼峰命名法映射 order_id --- orderId
mybatis-plus.configuration.map-underscore-to-camel-casetrue# 这个配置一定要加注意
spring.main.allow-bean-definition-overriding true7测试方法 Testvoid addOrder(){for (int i 0; i 9; i) {Order order new Order();order.setOrderId(Long.valueOf(1000i)). setOrderInfo(Sharding-Proxy success).setUserId(1001L);orderMapper.insert(order);}8查看数据库 Sharding-Proxy读写分离⭐
Docker搭建MySQL主从复制1主1从⭐
Master主节点配置
1运行一个mysql容器实例。作为Master节点如果没有mysql镜像则会自动拉取
docker run -p 3307:3306 \
-v /my-sql/mysql-master/log:/var/log/mysql \
-v /my-sql/mysql-master/data:/var/lib/mysql \
-v /my-sql/mysql-master/conf:/etc/mysql \
-e MYSQL_ROOT_PASSWORD123456 \
--name mysql-master \
-d mysql:5.72创建my.cnf文件也就是mysql的配置文件
vim /my-sql/mysql-master/conf/my.cnf将内容粘贴进my.cnf文件
[client]
# 指定编码格式为utf8,默认的MySQL会有中文乱码问题
default_character_setutf8
[mysqld]
collation_serverutf8_general_ci
character_set_serverutf8# 全局唯一id不允许有相同的
server_id200
binlog-ignore-dbmysql
# 指定MySQL二进制日志可以修改
log-binorder-mysql-bin
# binlog最大容量
binlog_cache_size1M
# 二进制日志格式这里指定的是混合日志
binlog_formatmixed
# binlog的有效期单位天
expire_logs_days7
slave_skip_errors10623重启该mysql容器实例
docker restart mysql-master4进入容器内部并登陆mysql密码默认是123456
$ docker exec -it mysql-master /bin/bash
$ mysql -uroot -p5在Master节点的MySQL中创建用户和分配权限
在主数据库创建的该帐号密码只是用来进行同步数据。
create user slave% identified by 123456;grant replication slave, replication client on *.* to slave%;Slave从节点配置
1运行一个MySQL容器实例作为slave节点从节点
docker run -p 3308:3306 \
-v /my-sql/mysql-slave/log:/var/log/mysql \
-v /my-sql/mysql-slave/data:/var/lib/mysql \
-v /my-sql/mysql-slave/conf:/etc/mysql \
-e MYSQL_ROOT_PASSWORD123456 \
--name mysql-slave \
-d mysql:5.72创建my.cnf文件也就是mysql的配置文件
vim /my-sql/mysql-slave/conf/my.cnf将内容粘贴进my.cnf文件
[client]
# 指定编码格式为utf8,默认的MySQL会有中文乱码问题
default_character_setutf8
[mysqld]
collation_serverutf8_general_ci
character_set_serverutf8# 全局唯一id不允许有相同的
server_id201
binlog-ignore-dbmysql
# 指定MySQL二进制日志可以修改
log-binorder-mysql-bin
# binlog最大容量
binlog_cache_size1M
# 二进制日志格式这里指定的是混合日志
binlog_formatmixed
# binlog的有效期单位天
expire_logs_days7
slave_skip_errors1062
# 表示slave将复制事件写进自己的二进制日志
log_slave_updates1
# 表示从机只能读
read_only13重启该mysql容器实例
docker restart mysql-slave4查看容器实例是否都是up
[rootk8s-master ~]# docker ps | grep mysql
3be6e547ab4e mysql:5.7 docker-entrypoint.s… About a minute ago Up 24 seconds 33060/tcp, 0.0.0.0:3308-3306/tcp, :::3308-3306/tcp mysql-slave
214fed096342 mysql:5.7 docker-entrypoint.s… 7 minutes ago Up 4 minutes 33060/tcp, 0.0.0.0:3307-3306/tcp, :::3307-3306/tcp mysql-master5进入从机MySQL
$ docker exec -it mysql-slave /bin/bash
$ mysql -uroot -p6查询Master数据库所在的服务器复制起来
[Master数据库所在的服务器 ~]# ifconfig
ens33: flags4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500inet 192.168.184.100 netmask 255.255.255.0 broadcast 192.168.184.255inet6 fe80::224c:e6cc:c9ab:f4e0 prefixlen 64 scopeid 0x20linkether 00:0c:29:af:f8:9f txqueuelen 1000 (Ethernet)RX packets 113915 bytes 164657385 (157.0 MiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 12073 bytes 970949 (948.1 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 07在从数据库slave配置主从同步记住下面这个命令要在从slave数据库执行
在Master节点中找到ens33的ip地址并放到下面的master_host中记住这个ip是Master数据库所在的服务器ip不是从Slave数据库的ip
change master to master_host192.168.184.100,master_userslave,master_password123456,master_port3307,master_log_fileorder-mysql-bin.000001,master_log_pos617,master_connect_retry30;配置参数解析 master_host主数据库Master的 ip 地址 master_user在Master数据库中创建的用来进行同步的帐号 master_password在Master数据库中创建的用来进行同步的帐号的密码 master_portMaster数据库的 MySQL端口号这里是3307 master_log_fileMySQL的 binlog文件名 master_log_posbinlog读取位置
8在从数据库slave查看主从同步状态
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Master_Host: 192.168.184.100Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 617Relay_Log_File: 3be6e547ab4e-relay-bin.000001Relay_Log_Pos: 4Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: NoSlave_SQL_Running: NoReplicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0Last_Error: Skip_Counter: 0Exec_Master_Log_Pos: 617Relay_Log_Space: 154Until_Condition: NoneUntil_Log_File: Until_Log_Pos: 0Master_SSL_Allowed: NoMaster_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: NoLast_IO_Errno: 0Last_IO_Error: Last_SQL_Errno: 0Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 0Master_UUID: Master_Info_File: /var/lib/mysql/master.infoSQL_Delay: 0SQL_Remaining_Delay: NULLSlave_SQL_Running_State: Master_Retry_Count: 86400Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version:
1 row in set (0.15 sec)ERROR:
No query specified我们找到里面的Slave_IO_Running: NoSlave_SQL_Running: No属性发现都是No的状态证明主从同步还没有开始。。。
9在从数据库slave正式开启主从同步
start slave;10再次在从数据库中查看主从同步状态
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.184.100Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 617Relay_Log_File: 3be6e547ab4e-relay-bin.000002Relay_Log_Pos: 326Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: YesSlave_SQL_Running: YesReplicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0Last_Error: Skip_Counter: 0Exec_Master_Log_Pos: 617Relay_Log_Space: 540Until_Condition: NoneUntil_Log_File: Until_Log_Pos: 0Master_SSL_Allowed: NoMaster_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: NoLast_IO_Errno: 0Last_IO_Error: Last_SQL_Errno: 0Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 200Master_UUID: a606bab7-1736-11ed-9207-0242ac110002Master_Info_File: /var/lib/mysql/master.infoSQL_Delay: 0SQL_Remaining_Delay: NULLSlave_SQL_Running_State: Slave has read all relay log; waiting for more updatesMaster_Retry_Count: 86400Master_Bind: Last_IO_Error_Timestamp: Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version:
1 row in set (0.09 sec)ERROR:
No query specified我们可以看到已经都为yes了说明主从同步已经开启。
也可以用Navicat去连接这两个数据库。如果Navicat出现连接不了docker的mysql则可以
方法一关闭防火墙测试环境用生产环境不可以用
sudo systemctl stop firewalld方法二开放防火墙对应端口比如master数据库的3307和slave数据库的3308生产环境用这个
主从同步失败问题Slave_SQL_Running:No
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.184.132Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 3752Relay_Log_File: 2c4136668536-relay-bin.000002Relay_Log_Pos: 326Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: YesSlave_SQL_Running: NoReplicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 1007Last_Error: Error Cant create database mall; database exists on query. Default database: mall. Query: create database mallSlave_SQL_Running为No的状态那么这是为什么呢可以看到Last_Error: Error ‘Can’t create database ‘mall’; database exists’ on query. Default database: ‘mall’. Query: ‘create database mall’原因是主数据库Master和从数据库slave不一致造成的我在从数据库执行了命令导致数据不一致最终导致主从复制失败。
Slave_SQL_Running:No的解决办法
1把主数据库和从数据库变成一模一样也就是把多余的数据库和表删除掉变成默认的mysql状态。切记生产环境下要做好数据备份
2结束同步
stop slave;3再次开启同步
start slave;4搞定
mysql show slave status \G;
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.184.132Master_User: slaveMaster_Port: 3307Connect_Retry: 30Master_Log_File: order-mysql-bin.000001Read_Master_Log_Pos: 3752Relay_Log_File: 2c4136668536-relay-bin.000003Relay_Log_Pos: 326Relay_Master_Log_File: order-mysql-bin.000001Slave_IO_Running: YesSlave_SQL_Running: Yes给Master和Slave的MySQL各自插入一张表⭐
数据库orderdb1
CREATE DATABASE orderdb1;数据库表orderdb1.order
SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS 0;DROP TABLE IF EXISTS order;
CREATE TABLE order (order_id bigint(20) NOT NULL,order_info varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,user_id bigint(20) NOT NULL,PRIMARY KEY (order_id) USING BTREE
) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_general_ci ROW_FORMAT DYNAMIC;SET FOREIGN_KEY_CHECKS 1;查看数据库
开始配置Sharding-Proxy读写分离⭐
1如果刚刚启动了Sharding-Proxy则先stop一下
[rootk8s-master bin]# pwd
/root/sharding-proxy/sharding-proxy-4.1.1/bin
[rootk8s-master bin]# ./stop.sh2删除config-master_slave.yaml文件
rm -rf /root/sharding-proxy/sharding-proxy-4.1.1/conf/config-master_slave.yaml3重新编辑config-master_slave.yaml文件
vi /root/sharding-proxy/sharding-proxy-4.1.1/conf/config-master_slave.yaml内容如下
# 设置sharding-proxy读写分离代理数据库默认为master_slave_db
schemaName: master_slave_db# 配置数据源
dataSources:master_ds: # 定义一个名为master_ds的数据源url: jdbc:mysql://192.168.184.100:3307/orderdb1?serverTimezoneUTCuseSSLfalseusername: rootpassword: 123456connectionTimeoutMilliseconds: 30000idleTimeoutMilliseconds: 60000maxLifetimeMilliseconds: 1800000maxPoolSize: 50slave_ds_1: # 定义一个名为slave_ds_1的数据源url: jdbc:mysql://192.168.184.100:3308/orderdb1?serverTimezoneUTCuseSSLfalseusername: rootpassword: 123456connectionTimeoutMilliseconds: 30000idleTimeoutMilliseconds: 60000maxLifetimeMilliseconds: 1800000maxPoolSize: 50
masterSlaveRule: #这里才是真正配置读写分离的配置name: ms_ds01masterDataSourceName: master_ds #配置master主数据源名称在上面配置数据源可以找到slaveDataSourceNames: #配置slave从数据源的集合在上面配置数据源可以找到- slave_ds_1 # 从数据源名称4启动sharding-proxy
[rootk8s-master bin]# pwd
/root/sharding-proxy/sharding-proxy-4.1.1/bin
[rootk8s-master bin]# ./start.sh 3366
Starting the Sharding-Proxy ...
The port is 3366
The classpath is /root/sharding-proxy/sharding-proxy-4.1.1/conf:.:..:/root/sharding-proxy/sharding-proxy-4.1.1/lib/*:/root/sharding-proxy/sharding-proxy-4.1.1/lib/*:/root/sharding-proxy/sharding-proxy-4.1.1/ext-lib/*
Please check the STDOUT file: /root/sharding-proxy/sharding-proxy-4.1.1/logs/stdout.log5application.properties
#关闭shardingsphere-JDBC由于我们不使用shardingsphere-JDBC所以需要先关闭
spring.shardingsphere.enabledfalse# 配置普通的JDBC数据源去连接sharding-proxy的读写分离代理数据库master_slave_db
spring.datasource.typecom.alibaba.druid.pool.DruidDataSource
spring.datasource.driver-class-namecom.mysql.jdbc.Driver
# 将url换成sharding-proxy代理数据库的IP和端口3366数据库统一换成master_slave_dbsharding-proxy的读写分离代理数据库-----重点
spring.datasource.urljdbc:mysql://192.168.184.100:3366/master_slave_db?useSSLfalseautoReconnecttruecharacterEncodingUTF-8serverTimezoneUTC
# sharding-proxy的账号
spring.datasource.usernameroot
# sharding-proxy的密码
spring.datasource.passwordroot# 在映射实体或者属性时将数据库中表名和字段名中的下划线去掉按照驼峰命名法映射 order_id --- orderId
mybatis-plus.configuration.map-underscore-to-camel-casetrue# 这个配置一定要加注意
spring.main.allow-bean-definition-overriding true6测试方法 //测试主从同步读写分离写操作Testvoid addOrder(){Order order new Order();order.setOrderId(Long.valueOf(166666)).setOrderInfo(测试sharding-proxy主从复制-读写分离).setUserId(1002L);orderMapper.insert(order);}// 测试读写分离读操作Testvoid selectOrder(){ListOrder orders orderMapper.selectList(null);orders.forEach(System.out::println);}
