mysql-utilities工具体验

2024-03-25 12:38

本文主要是介绍mysql-utilities工具体验,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

转载地址:http://yueliangdao0608.blog.51cto.com/397025/1199960


我主要体验了下几个关于REPLICATION的工具。 其他的可以参见手册。

先说下我的环境:

MASTER: 192.168.1.131

SLAVE: 192.168.1.132, 192.168.1.133

三台DB都有对外的ALL权限用户。

各个配置文件如下,


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
[root@mysql56-master home]# cat /etc/my.cnf
[mysqld]
user = ytt
skip- name -resolve
innodb_buffer_pool_size = 128M
basedir = /usr/ local /mysql
datadir = /usr/ local /mysql/data
port = 3306
server_id = 131
socket = /tmp/mysql.sock
explicit_defaults_for_timestamp
log-bin=mysql56-master-bin
binlog- ignore -db=mysql
gtid-mode= on
enforce-gtid-consistency
log-slave-updates
binlog-format=ROW
sync-master-info=1
report-host=192.168.1.131
report-port=3306
master_info_repository= table
relay_log_info_repository= table


其他两台SERVER,除了SERVER-ID,都基本相同,我就不贴了。


1. MYSQLREPLICATE 搭建主从的脚本,这里我搭建了两台从机。


1
2
3
4
5
6
7
8
9
10
11
12
mysqlreplicate --master=root:root@192.168.1.131:3306 --slave=root:root@192.168.1.132:3306;...
[root@mysql56-master home]# ./replicate_create
# master on 192.168.1.131: ... connected.
# slave on 192.168.1.132: ... connected.
# Checking for binary logging on master...
# Setting up replication...
# ...done.
# master on 192.168.1.131: ... connected.
# slave on 192.168.1.133: ... connected.
# Checking for binary logging on master...
# Setting up replication...
# ...done.


2. mysqlrplcheck  检查主从的运行情况。


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
[root@mysql56-master home]# mysqlrplcheck --master=root:root@192.168.1.131:3306 --slave=root:root@192.168.1.132:3306 -s
# master on 192.168.1.131: ... connected.
# slave on 192.168.1.132: ... connected.
Test Description                                                     Status
---------------------------------------------------------------------------
Checking for binary logging on master                                [pass]
Are there binlog exceptions?                                         [WARN]
+ ---------+--------+------------+
| server  | do_db  | ignore_db  |
+ ---------+--------+------------+
| master  |        | mysql      |
| slave   |        | mysql      |
+ ---------+--------+------------+
Replication user exists?                                             [pass]
Checking server_id values                                            [pass]
Checking server_uuid values                                          [pass]
Is slave connected to master?                                        [pass]
Check master information file                                        [pass]
Checking InnoDB compatibility                                        [pass]
Checking storage engines compatibility                               [pass]
Checking lower_case_table_names settings                             [pass]
Checking slave delay (seconds behind master)                         [pass]
#
# Slave status:
#
                 Slave_IO_State : Waiting for master to send event
                    Master_Host : 192.168.1.131
                    Master_User : rpl
                    Master_Port : 3306
                  Connect_Retry : 60
                Master_Log_File : mysql56-master-bin.000002
            Read_Master_Log_Pos : 151
                 Relay_Log_File : mysql56-slave-relay-bin.000003
                  Relay_Log_Pos : 379
          Relay_Master_Log_File : mysql56-master-bin.000002
               Slave_IO_Running : Yes
              Slave_SQL_Running : Yes
                Replicate_Do_DB :
            Replicate_Ignore_DB : mysql
             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 : 151
                Relay_Log_Space : 819
                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 : 131
                    Master_UUID : 4d89ad1d-bc12-11e2-87e9-080027338857
               Master_Info_File : mysql.slave_master_info
                      SQL_Delay : 0
            SQL_Remaining_Delay : None
        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 : 1
# ...done.


3. mysqlrplshow. 显示主从的架构。


1
2
3
4
5
6
7
8
9
10
[root@mysql56-master home]# mysqlrplshow --master=root:root@192.168.1.131:3306 --discover-slaves-login=root:root -v
# master on 192.168.1.131: ... connected.
# Finding slaves for master: 192.168.1.131:3306
# Replication Topology Graph
192.168.1.131:3306 (MASTER)
    |
    + --- 192.168.1.132:3306 [IO running: Yes] - (SLAVE)
    |
    + --- 192.168.1.133:3306 [IO running: Yes] - (SLAVE)
[root@mysql56-master home]#



4. mysqlfailover. 监视主从健康状态。


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
[root@mysql56-master home]# mysqlfailover --master=root:root@192.168.1.131:3306 --discover-slaves-login=root:root
# Discovering slaves for master at 192.168.1.131:3306
# Discovering slave at 192.168.1.132:3306
# Found slave: 192.168.1.132:3306
# Discovering slave at 192.168.1.133:3306
# Found slave: 192.168.1.133:3306
# Checking privileges .
MySQL Replication Failover Utility
Failover Mode = auto     Next Interval = Tue May 14 12:27:56 2013
Master Information
------------------
Binary Log File       Position  Binlog_Do_DB  Binlog_Ignore_DB
mysql56-master-bin.0  151                     mysql           
GTID Executed Set
None
Replication Health Status
+ ----------------+-------+---------+--------+------------+-------------------------------------------+
| host           | port  | role    | state  | gtid_mode  | health                                    |
+ ----------------+-------+---------+--------+------------+-------------------------------------------+
| 192.168.1.131  | 3306  | MASTER  | UP     | ON         | OK                                        |
| 192.168.1.132  | 3306  | SLAVE   | UP     | ON         | OK                                        |
| 192.168.1.133  | 3306  | SLAVE   | UP     | ON         | Binary log and Relay log filters differ.  |
+ ----------------+-------+---------+--------+------------+-------------------------------------------+
Q-quit R-refresh H-health G-GTID Lists U-UUIDs
[root@mysql56-master home]#



5. mysqlrpladmin. 对主从进行管理。

停止从机服务:

1
2
3
4
5
6
7
[root@mysql56-master home]# mysqlrpladmin  --master=root:root@192.168.1.131:3306 --slaves=root:root@192.168.1.132:3306,root:root@192.168.1.133:3306  stop
# Checking privileges .
# Performing STOP on all slaves.
#   Executing stop on slave 192.168.1.132:3306 Ok
#   Executing stop on slave 192.168.1.133:3306 Ok
# ...done.
[root@mysql56-master home]#

开启从机服务:

1
2
3
4
5
6
7
[root@mysql56-master home]# mysqlrpladmin  --master=root:root@192.168.1.131:3306 --slaves=root:root@192.168.1.132:3306,root:root@192.168.1.133:3306  stop
# Checking privileges .
# Performing STOP on all slaves.
#   Executing stop on slave 192.168.1.132:3306 Ok
#   Executing stop on slave 192.168.1.133:3306 Ok
# ...done.
[root@mysql56-master home]#


选择最好的备机准备以后切换用.

1
2
3
4
5
6
[root@mysql56-master home]# mysqlrpladmin --master=root:root@192.168.1.131:3306 --slaves=root:root@192.168.1.132:3306,root:root@192.168.1.133:3306 elect
# Checking privileges .
# Electing candidate slave from known slaves.
# Best slave found is located on 192.168.1.132:3306.
# ...done.
[root@mysql56-master home]#

进行主从切换。



1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
[root@mysql56-master home]#  mysqlrpladmin --master=root:root@192.168.1.131:3306 --slaves=root:root@192.168.1.132:3306,root:root@192.168.1.133:3306  --new-master=root:root@192.168.1.132:3306  --demote-master switchover  
# Checking privileges .
# Performing switchover from master at 192.168.1.131:3306 to slave at 192.168.1.132:3306.
# Checking candidate slave prerequisites.
# Checking slaves configuration to master.
# Waiting for slaves to catch up to old master.
# Stopping slaves.
# Performing STOP on all slaves.
# Demoting old master to be a slave to the new master.
# Switching slaves to new master.
# Starting all slaves.
# Performing START on all slaves.
# Checking slaves for errors.
# Switchover complete.
#
# Replication Topology Health:
+ ----------------+-------+---------+--------+------------+-----------------------------+
| host           | port  | role    | state  | gtid_mode  | health                      |
+ ----------------+-------+---------+--------+------------+-----------------------------+
| 192.168.1.132  | 3306  | MASTER  | UP     | ON         | OK                          |
| 192.168.1.131  | 3306  | SLAVE   | UP     | ON         | OK                          |
| 192.168.1.133  | 3306  | SLAVE   | UP     | ON         | OK                          |
+ ----------------+-------+---------+--------+------------+-----------------------------+
# ...done.
[root@mysql56-master home]#


显示下新的主从架构:


1
2
3
4
5
6
7
8
9
10
[root@mysql56-master home]# mysqlrplshow --master=root:root@192.168.1.132:3306 --discover-slaves-login=root:root -v
# master on 192.168.1.132: ... connected.
# Finding slaves for master: 192.168.1.132:3306
# Replication Topology Graph
192.168.1.132:3306 (MASTER)
    |
    + --- 192.168.1.131:3306 [IO running: Yes] - (SLAVE)
    |
    + --- 192.168.1.133:3306 [IO running: Yes] - (SLAVE)
[root@mysql56-master home]#


本文出自 “上帝,咱们不见不散!” 博客,请务必保留此出处http://yueliangdao0608.blog.51cto.com/397025/1199960


这篇关于mysql-utilities工具体验的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/845038

相关文章

MySQL双主搭建+keepalived高可用的实现

《MySQL双主搭建+keepalived高可用的实现》本文主要介绍了MySQL双主搭建+keepalived高可用的实现,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,... 目录一、测试环境准备二、主从搭建1.创建复制用户2.创建复制关系3.开启复制,确认复制是否成功4.同

MyBatis 动态 SQL 优化之标签的实战与技巧(常见用法)

《MyBatis动态SQL优化之标签的实战与技巧(常见用法)》本文通过详细的示例和实际应用场景,介绍了如何有效利用这些标签来优化MyBatis配置,提升开发效率,确保SQL的高效执行和安全性,感... 目录动态SQL详解一、动态SQL的核心概念1.1 什么是动态SQL?1.2 动态SQL的优点1.3 动态S

Python基于wxPython和FFmpeg开发一个视频标签工具

《Python基于wxPython和FFmpeg开发一个视频标签工具》在当今数字媒体时代,视频内容的管理和标记变得越来越重要,无论是研究人员需要对实验视频进行时间点标记,还是个人用户希望对家庭视频进行... 目录引言1. 应用概述2. 技术栈分析2.1 核心库和模块2.2 wxpython作为GUI选择的优

Mysql表的简单操作(基本技能)

《Mysql表的简单操作(基本技能)》在数据库中,表的操作主要包括表的创建、查看、修改、删除等,了解如何操作这些表是数据库管理和开发的基本技能,本文给大家介绍Mysql表的简单操作,感兴趣的朋友一起看... 目录3.1 创建表 3.2 查看表结构3.3 修改表3.4 实践案例:修改表在数据库中,表的操作主要

mysql出现ERROR 2003 (HY000): Can‘t connect to MySQL server on ‘localhost‘ (10061)的解决方法

《mysql出现ERROR2003(HY000):Can‘tconnecttoMySQLserveron‘localhost‘(10061)的解决方法》本文主要介绍了mysql出现... 目录前言:第一步:第二步:第三步:总结:前言:当你想通过命令窗口想打开mysql时候发现提http://www.cpp

MySQL大表数据的分区与分库分表的实现

《MySQL大表数据的分区与分库分表的实现》数据库的分区和分库分表是两种常用的技术方案,本文主要介绍了MySQL大表数据的分区与分库分表的实现,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有... 目录1. mysql大表数据的分区1.1 什么是分区?1.2 分区的类型1.3 分区的优点1.4 分

MySQL错误代码2058和2059的解决办法

《MySQL错误代码2058和2059的解决办法》:本文主要介绍MySQL错误代码2058和2059的解决办法,2058和2059的错误码核心都是你用的客户端工具和mysql版本的密码插件不匹配,... 目录1. 前置理解2.报错现象3.解决办法(敲重点!!!)1. php前置理解2058和2059的错误

Mysql删除几亿条数据表中的部分数据的方法实现

《Mysql删除几亿条数据表中的部分数据的方法实现》在MySQL中删除一个大表中的数据时,需要特别注意操作的性能和对系统的影响,本文主要介绍了Mysql删除几亿条数据表中的部分数据的方法实现,具有一定... 目录1、需求2、方案1. 使用 DELETE 语句分批删除2. 使用 INPLACE ALTER T

MySQL INSERT语句实现当记录不存在时插入的几种方法

《MySQLINSERT语句实现当记录不存在时插入的几种方法》MySQL的INSERT语句是用于向数据库表中插入新记录的关键命令,下面:本文主要介绍MySQLINSERT语句实现当记录不存在时... 目录使用 INSERT IGNORE使用 ON DUPLICATE KEY UPDATE使用 REPLACE

MySQL Workbench 安装教程(保姆级)

《MySQLWorkbench安装教程(保姆级)》MySQLWorkbench是一款强大的数据库设计和管理工具,本文主要介绍了MySQLWorkbench安装教程,文中通过图文介绍的非常详细,对大... 目录前言:详细步骤:一、检查安装的数据库版本二、在官网下载对应的mysql Workbench版本,要是