mysql主从误重复创建用户报错1396处理

最新推荐文章于 2024-04-03 16:45:00 发布
置顶 最新推荐文章于 2024-04-03 16:45:00 发布
阅读量1.9k 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_42942173/article/details/103742788
版权

mysql主从误重复创建用户报错1396处理

问题：
在mysql主从或者mysql分布式架构某些时候主从中断，经分析发现重复创建用户导致。

场景一、
如在日常的维护中，在主从架构或者分布式的架构中，要创建某些维护用户。比如创建运维用户，这个应该主库创建用户即可，同时主从库针对此用户设置免密登录。但是管理员同学不小心在主库从库同时执行了创建用户语句。

场景二、
如上线前中在分布式架构一主多从多分片部署运维用户，创建用户在主节点上执行，但是另外一部分同学不知道，正好做了同城切换测试，结果也出现了恰巧出现了重建用户情况。

如何处理：
此种情况是特殊情况，下面以传统主从模拟此报错和处理步骤。

初始化主从：
主库
mysql> show slave hosts
±-----------±-------------±-----±-----------±-------------------------------------+
| Server_id | Host | Port | Master_id | Slave_UUID |
±-----------±-------------±-----±-----------±-------------------------------------+
| 2624197123 | xx.x.xxx.xx6 | 3819 | 2624198899 | 4677ee4c-1404-11ea-80dd-00505699b577 |
±-----------±-------------±-----±-----------±-------------------------------------+

mysql> show master status \G;
*************************** 1. row ***************************
File: mysql-bin.000001
Position: 154
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set:

从库

mysql> show slave status \G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: testdb11
Master_User: repusr
Master_Port: 3819
Connect_Retry: 60
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 154
Relay_Log_File: relay-bin.000002
Relay_Log_Pos: 367
Relay_Master_Log_File: mysql-bin.000001
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: 154
Relay_Log_Space: 568
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: 2624198899
Master_UUID: 845133e9-1404-11ea-a37b-005056991dcd
Master_Info_File: /mysqldata/mysql/data/data/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:
Auto_Position: 1
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)

ERROR:
No query specified

mysql> show master status \G;
*************************** 1. row ***************************
File: mysql-bin.000001
Position: 154
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set:
1 row in set (0.00 sec)

ERROR:
No query specified

主库
create table mysql(id int);
create table mysq2(id int);
create table mysq3(id int);

mysql> show master status \G;
*************************** 1. row ***************************
File: mysql-bin.000001
Position: 672
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set: 845133e9-1404-11ea-a37b-005056991dcd:1-3
1 row in set (0.00 sec)

从库

mysql> show slave status \G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: testdb1
Master_User: repusr
Master_Port: 3819
Connect_Retry: 60
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 672
Relay_Log_File: relay-bin.000002
Relay_Log_Pos: 885
Relay_Master_Log_File: mysql-bin.000001
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: 672
Relay_Log_Space: 1086
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: 2624198899
Master_UUID: 845133e9-1404-11ea-a37b-005056991dcd
Master_Info_File: /mysqldata/mysql/data/data/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: 845133e9-1404-11ea-a37b-005056991dcd:1-3
Executed_Gtid_Set: 845133e9-1404-11ea-a37b-005056991dcd:1-3
Auto_Position: 1
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:

主库同时创建相同用户：
从库创建会话：
mysql> create user testing@’%’;
Query OK, 0 rows affected (0.01 sec)

mysql> show master status \G;
*************************** 1. row ***************************
File: mysql-bin.000001
Position: 365
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set: 4677ee4c-1404-11ea-80dd-00505699b577:1,
845133e9-1404-11ea-a37b-005056991dcd:1-3

主库创建会话：
mysql> create user testing@’%’;
Query OK, 0 rows affected (0.00 sec)

mysql> show global variables like ‘%gtid%’;
±---------------------------------±------------------------------------------+
| Variable_name | Value |
±---------------------------------±------------------------------------------+
| binlog_gtid_simple_recovery | ON |
| enforce_gtid_consistency | ON |
| gtid_executed | 845133e9-1404-11ea-a37b-005056991dcd:1-4 |
| gtid_executed_compression_period | 1000 |

然后从库报错：
mysql> show slave status \G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: testdb1
Master_User: repusr
Master_Port: 3819
Connect_Retry: 60
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 883
Relay_Log_File: relay-bin.000002
Relay_Log_Pos: 885
Relay_Master_Log_File: mysql-bin.000001
Slave_IO_Running: Yes
Slave_SQL_Running: No
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 1396
Last_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 0 failed executing transaction ‘845133e9-1404-11ea-a37b-005056991dcd:4’ at master log mysql-bin.000001, end_log_pos 883. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
Skip_Counter: 0
Exec_Master_Log_Pos: 672
Relay_Log_Space: 1297
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: NULL
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 1396
Last_SQL_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 0 failed executing transaction ‘845133e9-1404-11ea-a37b-005056991dcd:4’ at master log mysql-bin.000001, end_log_pos 883. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
Replicate_Ignore_Server_Ids:
Master_Server_Id: 2624198899
Master_UUID: 845133e9-1404-11ea-a37b-005056991dcd
Master_Info_File: /mysqldata/mysql/data/data/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State:
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp: 191225 20:15:51
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set: 845133e9-1404-11ea-a37b-005056991dcd:1-4
Executed_Gtid_Set: 4677ee4c-1404-11ea-80dd-00505699b577:1,
845133e9-1404-11ea-a37b-005056991dcd:1-3
Auto_Position: 1
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)

ERROR:
No query specified

从库查询gtid
mysql> show global variables like ‘%gtid%’;
±---------------------------------±---------------------------------------------------------------------------------+
| Variable_name | Value |
±---------------------------------±---------------------------------------------------------------------------------+
| binlog_gtid_simple_recovery | ON |
| enforce_gtid_consistency | ON |
| gtid_executed | 4677ee4c-1404-11ea-80dd-00505699b577:1,
845133e9-1404-11ea-a37b-005056991dcd:1-3 |
| gtid_executed_compression_period | 1000 |
| gtid_mode | ON |
| gtid_owned | |
| gtid_purged | 845133e9-1404-11ea-a37b-005056991dcd:1-3 |
| session_track_gtids | OFF |
±---------------------------------±---------------------------------------------------------------------------------+
8 rows in set (0.00 sec)

查主库的845133e9-1404-11ea-a37b-005056991dcd:1-4事务：
[mysql@testdb1:/mysqllog]>mysqlbinlog -vv mysql-bin.000001
SET @@SESSION.GTID_NEXT= ‘845133e9-1404-11ea-a37b-005056991dcd:4’/!/;
CREATE USER ‘testing’@’%’ IDENTIFIED WITH ‘mysql_native_password’
SET @@SESSION.GTID_NEXT= ‘AUTOMATIC’ /* added by mysqlbinlog / /!*/;
DELIMITER ;
#End of log file

查询从库4677ee4c-1404-11ea-80dd-00505699b577:1事务
[mysql@testdb2:/mysqllog]>mysqlbinlog -vv mysql-bin.000001
SET @@SESSION.GTID_NEXT= ‘4677ee4c-1404-11ea-80dd-00505699b577:1’/!/;
CREATE USER ‘testing’@’%’ IDENTIFIED WITH ‘mysql_native_password’
SET @@SESSION.GTID_NEXT= ‘AUTOMATIC’ /* added by mysqlbinlog / /!*/;
DELIMITER ;
End of log file

确认是从库已经创建test@’%‘用户，要回放主库创建test@’%'创建用户动作就会失败。

如何处理：
从库
mysql> stop slave;
mysql> reset master;
Query OK, 0 rows affected (0.04 sec)

mysql> set global gtid_purged=‘845133e9-1404-11ea-a37b-005056991dcd:1-4’;
Query OK, 0 rows affected (0.00 sec)

mysql>start slave;

mysql> show slave status \G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: testdb1
Master_User: repusr
Master_Port: 3819
Connect_Retry: 60
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 883
Relay_Log_File: relay-bin.000003
Relay_Log_Pos: 454
Relay_Master_Log_File: mysql-bin.000001
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: 883
Relay_Log_Space: 1597
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: 2624198899
Master_UUID: 845133e9-1404-11ea-a37b-005056991dcd
Master_Info_File: /mysqldata/mysql/data/data/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: 845133e9-1404-11ea-a37b-005056991dcd:1-4
Executed_Gtid_Set: 845133e9-1404-11ea-a37b-005056991dcd:1-4
Auto_Position: 1
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:

从库
mysql> show master status \G;
*************************** 1. row ***************************
File: mysql-bin.000001
Position: 154
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set: 845133e9-1404-11ea-a37b-005056991dcd:1-4
1 row in set (0.00 sec)

ERROR:
No query specified

mysql>
mysql> show global variables like ‘%gtid%’;
±---------------------------------±-----------------------------------------+
| Variable_name | Value |
±---------------------------------±-----------------------------------------+
| binlog_gtid_simple_recovery | ON |
| enforce_gtid_consistency | ON |
| gtid_executed | 845133e9-1404-11ea-a37b-005056991dcd:1-4 |
| gtid_executed_compression_period | 1000 |
| gtid_mode | ON |
| gtid_owned | |
| gtid_purged | 845133e9-1404-11ea-a37b-005056991dcd:1-4 |
| session_track_gtids | OFF |
±---------------------------------±-----------------------------------------+
8 rows in set (0.00 sec)

mysql>

主库
mysql> show master status \G;
*************************** 1. row ***************************
File: mysql-bin.000001
Position: 883
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set: 845133e9-1404-11ea-a37b-005056991dcd:1-4
1 row in set (0.00 sec)

ERROR:
No query specified

mysql> show global variables like ‘%gtid%’;
±---------------------------------±------------------------------------------+
| Variable_name | Value |
±---------------------------------±------------------------------------------+
| binlog_gtid_simple_recovery | ON |
| enforce_gtid_consistency | ON |
| gtid_executed | 845133e9-1404-11ea-a37b-005056991dcd:1-4 |
| gtid_executed_compression_period | 1000 |
| gtid_mode | ON |
| gtid_owned | 845133e9-1404-11ea-a37b-005056991dcd:6#89 |
| gtid_purged | |
| session_track_gtids | OFF |
±---------------------------------±------------------------------------------+
8 rows in set (0.01 sec)

总结：
1、确认从库报错1396
Last_Errno: 1396
Last_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 0 failed executing transaction ‘845133e9-1404-11ea-a37b-005056991dcd:4’ at master log mysql-bin.000001, end_log_pos 883. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.
2、通过mysqlbinlog 查询相关的主库和从库gitd事务，确认是重复创建用户导致。
3、从库处理步骤：
mysql> stop slave;
mysql> reset master;
mysql> set global gtid_purged=‘845133e9-1404-11ea-a37b-005056991dcd:1-4’;
mysql>start slave;

weixin_42942173
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
详解mysql8.0创建用户授予权限报错解决方法
09-09
主要介绍了详解mysql8.0创建用户授予权限报错解决方法，小编觉得挺不错的，现在分享给大家，也给大家做个参考。一起跟随小编过来看看吧
mysql 主从中断 Last_Errno: 1396处理
Hehuyi_In的博客
11-05 5461
一、 问题背景 给主库一个用户重置了一下密码，突然收到告警主从同步中断了...登上从库检查发现报错如下 mysql> show slave status\G; ... Last_Errno: 1396 Last_Error: Error 'Operation ALTER USER failed for 'bakuser'@'localhost'' on query. Default d...
mysql5.7添加从库中断后处理
liujing666888的专栏
12-29 354
>show slave status\G; ************************** 1. row ***************************                Slave_IO_State: Waiting for master to send event                   Master_Host: XXXXXXXX         
mysql 报错 ERROR 1396 (HY000): Operation ALTER USER failed for root@localhost 解决方案
最新发布
段子手168的博客
04-03 2684
mysql 修改密码 ALTER USER 'root'@'localhost' IDENTIFIED BY '123'; 时，报错 ERROR 1396 (HY000): Operation ALTER USER failed for root@localhost 解决方案 mysql 报错 ERROR 1396 (HY000): Operation ALTER USER failed for root@localhost
mysql 1396错误_错误1396（HY000）：操作CREATE USER对于'jack'@'localhost'失败
weixin_35772723的博客
02-01 316
我似乎无法重新创建一个已删除的简单用户，即使以root用户身份在MySQL中也是如此。我的情况是：用户’jack’曾经存在，但是我从mysql.user中删除了它以重新创建它。我在那张桌子上看不到任何痕迹。如果我对其他随机用户名(例如“jimmy”)执行此命令，则该命令会正常工作(就像最初对“ jack”所做的一样)。我已经做了些什么来破坏用户“ jack”，以及如何撤销该破坏，以便重新创建“ j...
mysql 1396,MySQL Last_Errno: 1396
weixin_29184075的博客
03-17 810
MySQL 主备数据库切换报错1396处理方法，操作步骤如下：mysql> show slave status \G;*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 196.55.3.180Mas...
mysql主从报错 error1396_MySQL 跨版本主从复制时报错：ERROR 1794 (HY000): Slave is not configured or failed to initia...
weixin_35677065的博客
01-19 171
背景： zabbix 数据库迁移，搭建主从，主是5.6.25，从是5.7.15，流式备份应用 redo.log 之后，change master 和reset slave 时报出如下错误mysql> CHANGE MASTER TO-> MASTER_HOST='192.168.40.129',-> MASTER_USER='repl',-> MASTER_PA...
《深入理解MySQL主从原理32讲》推荐篇
01-19
作者：高鹏（网名八怪），《深入理解MySQL主从原理32讲》系列文的作者。2008年开始至今一直从事Oracle/MySQL相关工作，现任易极付高级DBA，Oracle Ocm。有丰富的数据库性能调优，故障诊断经验，并且对MySQL源码有...
mysql主从同步（二）
01-07
一：主mysql的my.ini配置 [mysql] # 设置mysql客户端默认字符集 default-character-set=utf8 [mysqld] #设置3306端口 port = 3306 # 设置mysql的安装目录 basedir=”D:\mysql\mysql-5.7.27-winx64″ # 设置mysql...
Mysql主从复制注意事项的讲解
12-15
一、报错error connecting to master ‘[email protected]:x’ – retry-time: 60 retries: 86400 今天搭建mysql主从复制，一直报这个错。我是在一台虚拟机上使用多实例创建的2个不同端口的数据库，查了很久，才解决。 1....
Last_Errno: 1396
weixin_33682790的博客
09-13 612
Last_Errno: 1396 Last_Error: Error 'Operation CREATE USER failed for 'usera63'@'%'' on query. Default database: 'ucenter'. Query: 'create user usera63' 原因：从数据库已经存在该用户 解决： drop user 'us...
mysql创建用户报错1396_ERROR 1396 (HY000)|MySQL创建用户报错 - Exception List
weixin_34275113的博客
02-18 920
mysql> CREATE USER 'root'@'localhost' IDENTIFIED BY 'password';ERROR 1396 (HY000): Operation CREATE USER failed for 'root'@'localhost'问题很可能源于手动修改过root'@'localhost'这条记录，导致关联数据未能一起修改。两种解决方案：Solution ...
mysql1396
qq_41725214的博客
07-23 3011
提示错误：ERROR 1396 (HY000): Operation RENAME USER failed for 'root'@'%' 为了避免mysql中的安全隐患，将默认的root用户重命名。 使用 rename user 命令修改root用户名失败， 改用update mysql用户下的user表后修改成功。      ...
mysql主从报错 error1396_mysql主从复制1236错误
weixin_39656853的博客
01-19 239
今天监控显示mysql主从复制出错了，信息如下：mysql> show slave status\G;*************************** 1. row ***************************Slave_IO_State:Master_Host: 192.168.33.230Master_User: replMaster_Port: 3306Connect_...
mysql ERROR:1396
tangzhiyongzaa的博客
07-09 5189
起因：   先删除用户，再创建用户，执行SQL： create user yong@localhost identified by '111111'异常：ERROR 1396 (HY000): Operation CREATE USER failed for 'yong'@'localhost'解决：flush privileges; drop user yong@localhost; flush...
mysql创建用户报错1396
计算机毕业论文源码，学生个人网页制作html源码。贴近用户做网络推广和互联网优化。
11-17 426
mysql如何创建新用户，例如创建一个sss 密码为123的用户 1、登录：mysql-uroot-p 2、查看现有用户，selecthost,user,authentication_stringfrommysql.user; 3、新建用户，createuser"sss"@"host"identifiedby"123...
MySQL创建用户提示1396
bisal的专栏
05-04 1385
MySQL中使用create user创建用户提示这个错误，ERROR1396(HY000):OperationCREATEUSERfailedfor'test'@'%'其中一种可能的原因，就是之前删除该用户的时候，用的delete删除的是数据字典表，如下所示，deletefrommysql.userwhereuser= 'test';针对这种情况，如果再创建相同的用户名...
mysql服务器失败1396_Mysql ERROR 1396 (HY000) 错误的解决办法
weixin_42588877的博客
01-28 9605
建立用户的时候报告这个错误：ERROR 1396 (HY000): Operation CREATE USER failed for ‘abc’@’localhost’原因是mysql中已经有了这个用户，从mysql.user中直接删除delete，然后刷新权限FLUSH PRIVILEGES，再建用户就不会有这个问题了。如果是drop user 的话，mysql内部会自动刷新一下，那么再建也不会...
主从SQL线程报错处理
nzy15854627832的博客
03-28 1254
场景： MySQL主从复制环境中，从库无法进行数据同步，Slave_SQL_Running: No 问题描述 在主库进行插入语句insert into 00db2.00bak21 values (10,'0021110');后，从库未查到这条数据信息,并且Slave_SQL_Running状态为No 查看从库状态，报错如下： Last_Errno: 1396 Last_Error: Coordinator stopped because there we...
mysql主从复制报错
06-03
2. 主从服务器之间的 MySQL 版本不一致，需要保持一致。 3. 主从服务器之间的时区设置不一致，可以通过执行命令 `SELECT @@global.time_zone, @@session.time_zone;` 来查看时区设置，并在两台服务器上保持一致。 ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值