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数据库聚簇索引与非聚簇索引举例详解

《Mysql数据库聚簇索引与非聚簇索引举例详解》在MySQL中聚簇索引和非聚簇索引是两种常见的索引结构,它们的主要区别在于数据的存储方式和索引的组织方式,:本文主要介绍Mysql数据库聚簇索引与非... 目录前言一、核心概念与本质区别二、聚簇索引(Clustered Index)1. 实现原理(以 Inno

sqlserver、mysql、oracle、pgsql、sqlite五大关系数据库的对象名称和转义字符

《sqlserver、mysql、oracle、pgsql、sqlite五大关系数据库的对象名称和转义字符》:本文主要介绍sqlserver、mysql、oracle、pgsql、sqlite五大... 目录一、转义符1.1 oracle1.2 sqlserver1.3 PostgreSQL1.4 SQLi

MySQL数据库双机热备的配置方法详解

《MySQL数据库双机热备的配置方法详解》在企业级应用中,数据库的高可用性和数据的安全性是至关重要的,MySQL作为最流行的开源关系型数据库管理系统之一,提供了多种方式来实现高可用性,其中双机热备(M... 目录1. 环境准备1.1 安装mysql1.2 配置MySQL1.2.1 主服务器配置1.2.2 从

深入理解Mysql OnlineDDL的算法

《深入理解MysqlOnlineDDL的算法》本文主要介绍了讲解MysqlOnlineDDL的算法,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面随着小... 目录一、Online DDL 是什么?二、Online DDL 的三种主要算法2.1COPY(复制法)

基于Python开发Windows自动更新控制工具

《基于Python开发Windows自动更新控制工具》在当今数字化时代,操作系统更新已成为计算机维护的重要组成部分,本文介绍一款基于Python和PyQt5的Windows自动更新控制工具,有需要的可... 目录设计原理与技术实现系统架构概述数学建模工具界面完整代码实现技术深度分析多层级控制理论服务层控制注

mysql8.0.43使用InnoDB Cluster配置主从复制

《mysql8.0.43使用InnoDBCluster配置主从复制》本文主要介绍了mysql8.0.43使用InnoDBCluster配置主从复制,文中通过示例代码介绍的非常详细,对大家的学习或者... 目录1、配置Hosts解析(所有服务器都要执行)2、安装mysql shell(所有服务器都要执行)3、

k8s中实现mysql主备过程详解

《k8s中实现mysql主备过程详解》文章讲解了在K8s中使用StatefulSet部署MySQL主备架构,包含NFS安装、storageClass配置、MySQL部署及同步检查步骤,确保主备数据一致... 目录一、k8s中实现mysql主备1.1 环境信息1.2 部署nfs-provisioner1.2.

MySQL中VARCHAR和TEXT的区别小结

《MySQL中VARCHAR和TEXT的区别小结》MySQL中VARCHAR和TEXT用于存储字符串,VARCHAR可变长度存储在行内,适合短文本;TEXT存储在溢出页,适合大文本,下面就来具体的了解... 目录一、VARCHAR 和 TEXT 基本介绍1. VARCHAR2. TEXT二、VARCHAR

MySQL中C接口的实现

《MySQL中C接口的实现》本节内容介绍使用C/C++访问数据库,包括对数据库的增删查改操作,主要是学习一些接口的调用,具有一定的参考价值,感兴趣的可以了解一下... 目录准备mysql库使用mysql库编译文件官方API文档对象的创建和关闭链接数据库下达sql指令select语句前言:本节内容介绍使用C/

mybatis直接执行完整sql及踩坑解决

《mybatis直接执行完整sql及踩坑解决》MyBatis可通过select标签执行动态SQL,DQL用ListLinkedHashMap接收结果,DML用int处理,注意防御SQL注入,优先使用#... 目录myBATiFBNZQs直接执行完整sql及踩坑select语句采用count、insert、u