Maxscale安装-读写分离(1)

前言

关于MySQL中间件的产品也很多,之前用过了360的Atlas、玩过MyCat。这边我选择 Maxscale的原因就是功能能满足需求,也看好他的未来发展。

其实有关于如何安装 Maxscale的文章百度一下一大把，写这篇文章主要为了说明配置的某些现象，同时也为之后使用Maxscale的其他配置做下基础。

我的环境

这边我的‘一主二从‘已经是搭建好的了，如何搭建就不再描述了。

注意：这边我的三个节点都没有开启 GTID，具体是为什么在之后会讲到，这边大家留意一下就行。

192.168.137.11 (Maxscale)
192.168.137.21:3306 (Master)
192.168.137.22:3306 (Slave)
192.168.137.23:3306 (Slave)

1

2

3

4

192.168.137.11 (Maxscale)

192.168.137.21:3306 (Master)

192.168.137.22:3306 (Slave)

192.168.137.23:3306 (Slave)

这边我使用的用于复制的用户是maxscale,具体权限如下:

CREATE USER maxscale@‘%‘ IDENTIFIED BY "123456";
GRANT replication slave, replication client ON *.* TO maxscale@‘%‘;
GRANT SELECT ON mysql.* TO maxscale@‘%‘;
GRANT ALL ON maxscale_schema.* TO maxscale@‘%‘;
GRANT SHOW DATABASES ON *.* TO maxscale@‘%‘;

root@(none) 22:34:15>SELECT VERSION();
+--------------------+
| VERSION() |
+--------------------+
| 10.1.8-MariaDB-log |
+--------------------+
1 row in set (0.00 sec)

root@(none) 22:34:25>SHOW SLAVE HOSTS;
+------------+----------------+------+------------+
| Server_id | Host | Port | Master_id |
+------------+----------------+------+------------+
| 3306137022 | 192.168.137.21 | 3306 | 3306137021 |
| 3306137023 | 192.168.137.21 | 3306 | 3306137021 |
+------------+----------------+------+------------+
2 rows in set (0.00 sec)

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

CREATE USER maxscale@‘%‘ IDENTIFIED BY "123456";

GRANT replication slave, replication client ON *.* TO maxscale@‘%‘;

GRANT SELECT ON mysql.* TO maxscale@‘%‘;

GRANT ALL ON maxscale_schema.* TO maxscale@‘%‘;

GRANT SHOW DATABASES ON *.* TO maxscale@‘%‘;

root@(none) 22:34:15>SELECT VERSION();

+--------------------+

| VERSION()          |

+--------------------+

| 10.1.8-MariaDB-log |

+--------------------+

1 row in set (0.00 sec)

root@(none) 22:34:25>SHOW SLAVE HOSTS;

+------------+----------------+------+------------+

| Server_id  | Host           | Port | Master_id  |

+------------+----------------+------+------------+

| 3306137022 | 192.168.137.21 | 3306 | 3306137021 |

| 3306137023 | 192.168.137.21 | 3306 | 3306137021 |

+------------+----------------+------+------------+

2 rows in set (0.00 sec)

下载Maxscale

在 192.168.137.11 机器上

这边提供下载地址: https://downloads.mariadb.com

我的版本

[root@normal_11 opt]# pwd
/opt

[root@normal_11 opt]# ll
total 149624
-rw-r--r-- 1 root root 3587510 Nov 2 21:07 maxscale-2.0.1.centos.7.tar.gz

1

2

3

4

5

6

[root@normal_11 opt]# pwd

/opt

[root@normal_11 opt]# ll

total 149624

-rw-r--r--   1 root root   3587510 Nov  2 21:07 maxscale-2.0.1.centos.7.tar.gz

开始安装

[root@normal_11 opt]# groupadd maxscale
[root@normal_11 opt]# useradd -g maxscale maxscale
[root@normal_11 opt]# cd /opt
[root@normal_11 opt]# tar -zxf maxscale-2.0.1.centos.7.tar.gz
[root@normal_11 opt]# ln -s maxscale-2.0.1.centos.7 /usr/local/maxscale
[root@normal_11 opt]# chown -R maxscale:maxscale /usr/local/maxscale
[root@normal_11 opt]# mkdir -p /u01/maxscale/{data,cache,logs,tmp}
[root@normal_11 opt]# mkdir -p /u01/maxscale/logs/{binlog,trace}
[root@normal_11 opt]# chown -R maxscale:maxscale /u01/maxscale
[root@normal_11 opt]# /usr/local/maxscale/bin/maxkeys /u01/maxscale/data/
[root@normal_11 opt]# /usr/local/maxscale/bin/maxpasswd /u01/maxscale/data/.secrets 123456
1D30C1E689410756D7B82C233FCBF8D9

1

2

3

4

5

6

7

8

9

10

11

12

[root@normal_11 opt]# groupadd maxscale

[root@normal_11 opt]# useradd -g maxscale maxscale

[root@normal_11 opt]# cd /opt

[root@normal_11 opt]# tar -zxf maxscale-2.0.1.centos.7.tar.gz

[root@normal_11 opt]# ln -s maxscale-2.0.1.centos.7 /usr/local/maxscale

[root@normal_11 opt]# chown -R maxscale:maxscale /usr/local/maxscale

[root@normal_11 opt]# mkdir -p /u01/maxscale/{data,cache,logs,tmp}

[root@normal_11 opt]# mkdir -p /u01/maxscale/logs/{binlog,trace}

[root@normal_11 opt]# chown -R maxscale:maxscale /u01/maxscale

[root@normal_11 opt]# /usr/local/maxscale/bin/maxkeys /u01/maxscale/data/

[root@normal_11 opt]# /usr/local/maxscale/bin/maxpasswd /u01/maxscale/data/.secrets 123456

1D30C1E689410756D7B82C233FCBF8D9

Maxscale 配置文件

[root@normal_11 opt]# cat /etc/maxscale.cnf
###################################################
# CREATE USER maxscale@‘%‘ IDENTIFIED BY "123456";
# GRANT replication slave, replication client ON *.* TO maxscale@‘%‘;
# GRANT SELECT ON mysql.* TO maxscale@‘%‘;
# GRANT ALL ON maxscale_schema.* TO maxscale@‘%‘;
# GRANT SHOW DATABASES ON *.* TO maxscale@‘%‘;
# groupadd maxscale
# useradd -g maxscale maxscale
# cd /opt
# tar -zxf maxscale-2.0.1.rhel.7.tar.gz
# ln -s /opt/maxscale-2.0.1.rhel.7 /usr/local/maxscale
# chown -R maxscale:maxscale /usr/local/maxscale
# mkdir -p /u01/maxscale/{data,cache,logs,tmp}
# mkdir -p /u01/maxscale/logs/{binlog,trace}
# chown -R maxscale:maxscale /u01/maxscale
# /usr/local/maxscale/bin/maxkeys /u01/maxscale/data/
# /usr/local/maxscale/bin/maxpasswd /u01/maxscale/data/.secrets 123456
###################################################

[maxscale]
# 开启线程个数，默认为1.设置为auto会同cpu核数相同
threads=auto
# timestamp精度
ms_timestamp=1
# 将日志写入到syslog中
syslog=1
# 将日志写入到maxscale的日志文件中
maxlog=1
# 不将日志写入到共享缓存中，开启debug模式时可打开加快速度
log_to_shm=0
# 记录告警信息
log_warning=1
# 记录notice
log_notice=1
# 记录info
log_info=1
# 不打开debug模式
log_debug=0
# 日志递增
log_augmentation=1

# 相关目录设置
basedir=/usr/local/maxscale/
logdir=/u01/maxscale/logs/trace/
datadir=/u01/maxscale/data/
cachedir=/u01/maxscale/cache/
piddir=/u01/maxscale/tmp/

[server1]
type=server
address=192.168.137.21
port=3306
protocol=MySQLBackend
serv_weight=1

[server2]
type=server
address=192.168.137.22
port=3306
protocol=MySQLBackend
serv_weight=3

[server3]
type=server
address=192.168.137.23
port=3306
protocol=MySQLBackend
serv_weight=3

[MySQL Monitor]
type=monitor
module=mysqlmon
servers=server1,server2,server3
user=maxscale
passwd=1D30C1E689410756D7B82C233FCBF8D9
# 监控心态为 10s
monitor_interval=10000
# 当复制slave全部断掉时，maxscale仍然可用，将所有的访问指向master节点
detect_stale_master=true
# 监控主从复制延迟，可用后续指定router service的(配置此参数请求会永远落在 master)
# detect_replication_lag=true

[Read-Only Service]
type=service
router=readconnroute
servers=server1,server2,server3
user=maxscale
passwd=1D30C1E689410756D7B82C233FCBF8D9
router_options=slave
# 允许root用户登录执行
enable_root_user=1
# 查询权重
weightby=serv_weight

[Read-Write Service]
type=service
router=readwritesplit
servers=server1,server2,server3
user=maxscale
passwd=1D30C1E689410756D7B82C233FCBF8D9
max_slave_connections=100%
# sql语句中的存在变量只指向master中执行
use_sql_variables_in=master
# 允许root用户登录执行
enable_root_user=1
# 允许主从最大间隔(s)
max_slave_replication_lag=3600

[MaxAdmin Service]
type=service
router=cli

[Read-Only Listener]
type=listener
service=Read-Only Service
protocol=MySQLClient
port=4008

[Read-Write Listener]
type=listener
service=Read-Write Service
protocol=MySQLClient
port=4006

[MaxAdmin Listener]
type=listener
service=MaxAdmin Service
protocol=maxscaled
socket=/u01/maxscale/tmp/maxadmin.sock
port=6603

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

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

[root@normal_11 opt]# cat /etc/maxscale.cnf

###################################################

# CREATE USER [email protected]‘%‘ IDENTIFIED BY "123456";

# GRANT replication slave, replication client ON *.* TO [email protected]‘%‘;

# GRANT SELECT ON mysql.* TO [email protected]‘%‘;

# GRANT ALL ON maxscale_schema.* TO [email protected]‘%‘;

# GRANT SHOW DATABASES ON *.* TO [email protected]‘%‘;

# groupadd maxscale

# useradd -g maxscale maxscale

# cd /opt

# tar -zxf maxscale-2.0.1.rhel.7.tar.gz

# ln -s /opt/maxscale-2.0.1.rhel.7 /usr/local/maxscale

# chown -R maxscale:maxscale /usr/local/maxscale

# mkdir -p /u01/maxscale/{data,cache,logs,tmp}

# mkdir -p /u01/maxscale/logs/{binlog,trace}

# chown -R maxscale:maxscale /u01/maxscale

# /usr/local/maxscale/bin/maxkeys /u01/maxscale/data/

# /usr/local/maxscale/bin/maxpasswd /u01/maxscale/data/.secrets 123456

###################################################

[maxscale]

# 开启线程个数，默认为1.设置为auto会同cpu核数相同

threads=auto

# timestamp精度

ms_timestamp=1

# 将日志写入到syslog中

syslog=1

# 将日志写入到maxscale的日志文件中

maxlog=1

# 不将日志写入到共享缓存中，开启debug模式时可打开加快速度

log_to_shm=0

# 记录告警信息

log_warning=1

# 记录notice

log_notice=1

# 记录info

log_info=1

# 不打开debug模式

log_debug=0

# 日志递增

log_augmentation=1

# 相关目录设置

basedir=/usr/local/maxscale/

logdir=/u01/maxscale/logs/trace/

datadir=/u01/maxscale/data/

cachedir=/u01/maxscale/cache/

piddir=/u01/maxscale/tmp/

[server1]

type=server

address=192.168.137.21

port=3306

protocol=MySQLBackend

serv_weight=1

[server2]

type=server

address=192.168.137.22

port=3306

protocol=MySQLBackend

serv_weight=3

[server3]

type=server

address=192.168.137.23

port=3306

protocol=MySQLBackend

serv_weight=3

[MySQL Monitor]

type=monitor

module=mysqlmon

servers=server1,server2,server3

user=maxscale

passwd=1D30C1E689410756D7B82C233FCBF8D9

# 监控心态为 10s

monitor_interval=10000

# 当复制slave全部断掉时，maxscale仍然可用，将所有的访问指向master节点

detect_stale_master=true

# 监控主从复制延迟，可用后续指定router service的(配置此参数请求会永远落在 master)

# detect_replication_lag=true

[Read-Only Service]

type=service

router=readconnroute

servers=server1,server2,server3

user=maxscale

passwd=1D30C1E689410756D7B82C233FCBF8D9

router_options=slave

# 允许root用户登录执行

enable_root_user=1

# 查询权重

weightby=serv_weight

[Read-Write Service]

type=service

router=readwritesplit

servers=server1,server2,server3

user=maxscale

passwd=1D30C1E689410756D7B82C233FCBF8D9

max_slave_connections=100%

# sql语句中的存在变量只指向master中执行

use_sql_variables_in=master

# 允许root用户登录执行

enable_root_user=1

# 允许主从最大间隔(s)

max_slave_replication_lag=3600

[MaxAdmin Service]

type=service

router=cli

[Read-Only Listener]

type=listener

service=Read-Only Service

protocol=MySQLClient

port=4008

[Read-Write Listener]

type=listener

service=Read-Write Service

protocol=MySQLClient

port=4006

[MaxAdmin Listener]

type=listener

service=MaxAdmin Service

protocol=maxscaled

socket=/u01/maxscale/tmp/maxadmin.sock

port=6603

细心的朋友会注意到, 的我配置文件最上面就是安装 Maxscale 的基本步骤，这是本人的一个习惯.

这边我稍微说明一下配置文件的意思:

  1. [server1], [server2], [server3] 我配置了三个Maxscale需要连接的MySQL服务
  2. [MySQL Monitor] 配置一个监听服务, 同时监听着 [server1], [server2], [server3] 的状态
  3. [Read-Only Service] 配置了只读服务, 只在[server2], [server3]中执行

注意: 虽然是只读服务但是同样可以执行 DML DDL, 说以要限制好用户的权限.

  1. [Read-Write Listener] 配置了读写分离的服务
  2. [MaxAdmin Listener] 配置了用户管理Maxscale的服务

演示

这边我们以 [Read-Write Listener] 配置的服务来演示读写分离情况

  1. 启动 Maxscale

如果启动有报错那就查看一下日志 /var/log/message 或 /u01/maxscale/logs/trace/maxscale1.log(自定义)

[root@normal_11 opt]# /usr/local/maxscale/bin/maxscale -f /etc/maxscale.cnf
[root@normal_11 opt]# netstat -natpl | grep max
tcp 0 0 0.0.0.0:4008 0.0.0.0:* LISTEN 5507/maxscale
tcp 0 0 0.0.0.0:6603 0.0.0.0:* LISTEN 5507/maxscale
tcp 0 0 0.0.0.0:4006 0.0.0.0:* LISTEN 5507/maxscale
tcp 0 0 192.168.137.11:43102 192.168.137.22:3306 ESTABLISHED 5507/maxscale
tcp 0 0 192.168.137.11:54624 192.168.137.21:3306 ESTABLISHED 5507/maxscale
tcp 0 0 192.168.137.11:52989 192.168.137.23:3306 ESTABLISHED 5507/maxscale

1

2

3

4

5

6

7

8

[root@normal_11 opt]# /usr/local/maxscale/bin/maxscale -f /etc/maxscale.cnf

[root@normal_11 opt]# netstat -natpl | grep max

tcp        0      0 0.0.0.0:4008            0.0.0.0:*               LISTEN      5507/maxscale

tcp        0      0 0.0.0.0:6603            0.0.0.0:*               LISTEN      5507/maxscale

tcp        0      0 0.0.0.0:4006            0.0.0.0:*               LISTEN      5507/maxscale

tcp        0      0 192.168.137.11:43102    192.168.137.22:3306     ESTABLISHED 5507/maxscale

tcp        0      0 192.168.137.11:54624    192.168.137.21:3306     ESTABLISHED 5507/maxscale

tcp        0      0 192.168.137.11:52989    192.168.137.23:3306     ESTABLISHED 5507/maxscale
  1. 使用 maxadmin 查看服务

[root@normal_11 opt]# /usr/local/maxscale/bin/maxadmin -S /u01/maxscale/tmp/maxadmin.sock
MaxScale> list servers
Servers.
-------------------+-----------------+-------+-------------+--------------------
Server | Address | Port | Connections | Status
-------------------+-----------------+-------+-------------+--------------------
server1 | 192.168.137.21 | 3306 | 0 | Master, Running
server2 | 192.168.137.22 | 3306 | 0 | Slave, Running
server3 | 192.168.137.23 | 3306 | 0 | Slave, Running
-------------------+-----------------+-------+-------------+--------------------
MaxScale> list services
Services.
--------------------------+----------------------+--------+---------------
Service Name | Router Module | #Users | Total Sessions
--------------------------+----------------------+--------+---------------
Read-Only Service | readconnroute | 1 | 1
Read-Write Service | readwritesplit | 1 | 1
MaxAdmin Service | cli | 3 | 3
--------------------------+----------------------+--------+---------------

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

[root@normal_11 opt]# /usr/local/maxscale/bin/maxadmin -S /u01/maxscale/tmp/maxadmin.sock

MaxScale> list servers

Servers.

-------------------+-----------------+-------+-------------+--------------------

Server             | Address         | Port  | Connections | Status

-------------------+-----------------+-------+-------------+--------------------

server1            | 192.168.137.21  |  3306 |           0 | Master, Running

server2            | 192.168.137.22  |  3306 |           0 | Slave, Running

server3            | 192.168.137.23  |  3306 |           0 | Slave, Running

-------------------+-----------------+-------+-------------+--------------------

MaxScale> list services

Services.

--------------------------+----------------------+--------+---------------

Service Name              | Router Module        | #Users | Total Sessions

--------------------------+----------------------+--------+---------------

Read-Only Service         | readconnroute        |      1 |     1

Read-Write Service        | readwritesplit       |      1 |     1

MaxAdmin Service          | cli                  |      3 |     3

--------------------------+----------------------+--------+---------------

通过登录Maxscale的读写分离服务, 来执行sql并且查看日志，查看日志路由情况。

注意: 这边登录的用户就是普通的MySQL用户, 不是maxscale用户

[root@normal_11 opt]# mysql -uHH -p -h192.168.137.11 -P4006
Logging to file ‘/u01/mysql_history/query.log‘
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 5524
Server version: 5.5.5-10.0.0 2.0.1-maxscale MariaDB Server

Copyright (c) 2009-2015 Percona LLC and/or its affiliates
Copyright (c) 2000, 2015, <a href="http://www.ttlsa.com/oracle/" title="Oracle"target="_blank">Oracle</a> and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type ‘help;‘ or ‘\h‘ for help. Type ‘\c‘ to clear the current input statement.

HH@192.168.137.11 11:13:46 [(none)]>SELECT * FROM test.t1;
+----+------+-----+
| id | name | age |
+----+------+-----+
| 1 | HH1 | 1 |
| 2 | HH2 | 2 |
| 3 | HH3 | 3 |
+----+------+-----+
3 rows in set (0.01 sec)

HH@192.168.137.11 11:15:03 [(none)]>INSERT INTO test.t1 VALUES(NULL, ‘HH4‘, 4);
Query OK, 1 row affected (0.01 sec)

# 使用 HH 登录成的日志
2016-11-03 23:13:46.907 info : (log_server_connections): Servers and router connection counts:
2016-11-03 23:13:46.907 info : (log_server_connections): current operations : 0 in 192.168.137.21:3306 RUNNING MASTER
2016-11-03 23:13:46.907 info : (log_server_connections): current operations : 0 in 192.168.137.22:3306 RUNNING SLAVE
2016-11-03 23:13:46.907 info : (log_server_connections): current operations : 0 in 192.168.137.23:3306 RUNNING SLAVE
2016-11-03 23:13:46.908 info : (select_connect_backend_servers): Selected RUNNING MASTER in 192.168.137.21:3306
2016-11-03 23:13:46.908 info : (select_connect_backend_servers): Selected RUNNING SLAVE in 192.168.137.22:3306
2016-11-03 23:13:46.908 info : (select_connect_backend_servers): Selected RUNNING SLAVE in 192.168.137.23:3306
2016-11-03 23:13:46.908 info : (session_alloc): Started Read-Write Service client session [0] for ‘HH‘ from 192.168.137.11
2016-11-03 23:13:46.909 [9] info : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ|QUERY_TYPE_SYSVAR_READ, stmt: select @@version_comment limit 1
2016-11-03 23:13:46.909 [9] info : (route_single_stmt): Route query to master 192.168.137.21:3306 <
2016-11-03 23:13:46.922 [9] info : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ, stmt: select USER()
2016-11-03 23:13:46.922 [9] info : (route_single_stmt): Route query to slave 192.168.137.22:3306 <

# 执行 SELECT * FROM test.t1 语句被路由到 192.168.137.22:3306[server2]中的日志
2016-11-03 23:15:02.618 [9] info : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ, stmt: SELECT * FROM test.t1
2016-11-03 23:15:02.618 [9] info : (route_single_stmt): Route query to slave 192.168.137.22:3306 <

# 执行 INSERT INTO test.t1 VALUES(NULL, ‘HH4‘, 4) 语句被路由到 192.168.137.21:3306[server1]中的日志
2016-11-03 23:17:02.716 [9] info : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_WRITE, stmt: INSERT INTO test.t1 VALUES(NULL, ‘HH4‘, 4)
2016-11-03 23:17:02.716 [9] info : (route_single_stmt): Route query to master 192.168.137.21:3306 <

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

[root@normal_11 opt]# mysql -uHH -p -h192.168.137.11 -P4006

Logging to file ‘/u01/mysql_history/query.log‘

Enter password:

Welcome to the MySQL monitor.  Commands end with ; or \g.

Your MySQL connection id is 5524

Server version: 5.5.5-10.0.0 2.0.1-maxscale MariaDB Server

Copyright (c) 2009-2015 Percona LLC and/or its affiliates

Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type ‘help;‘ or ‘\h‘ for help. Type ‘\c‘ to clear the current input statement.

HH@192.168.137.11 11:13:46 [(none)]>SELECT * FROM test.t1;

+----+------+-----+

| id | name | age |

+----+------+-----+

|  1 | HH1  |   1 |

|  2 | HH2  |   2 |

|  3 | HH3  |   3 |

+----+------+-----+

3 rows in set (0.01 sec)

HH@192.168.137.11 11:15:03 [(none)]>INSERT INTO test.t1 VALUES(NULL, ‘HH4‘, 4);

Query OK, 1 row affected (0.01 sec)

# 使用 HH 登录成的日志

2016-11-03 23:13:46.907   info   : (log_server_connections): Servers and router connection counts:

2016-11-03 23:13:46.907   info   : (log_server_connections): current operations : 0 in  192.168.137.21:3306 RUNNING MASTER

2016-11-03 23:13:46.907   info   : (log_server_connections): current operations : 0 in  192.168.137.22:3306 RUNNING SLAVE

2016-11-03 23:13:46.907   info   : (log_server_connections): current operations : 0 in  192.168.137.23:3306 RUNNING SLAVE

2016-11-03 23:13:46.908   info   : (select_connect_backend_servers): Selected RUNNING MASTER in         192.168.137.21:3306

2016-11-03 23:13:46.908   info   : (select_connect_backend_servers): Selected RUNNING SLAVE in  192.168.137.22:3306

2016-11-03 23:13:46.908   info   : (select_connect_backend_servers): Selected RUNNING SLAVE in  192.168.137.23:3306

2016-11-03 23:13:46.908   info   : (session_alloc): Started Read-Write Service client session [0] for ‘HH‘ from 192.168.137.11

2016-11-03 23:13:46.909   [9]  info   : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ|QUERY_TYPE_SYSVAR_READ, stmt: select @@version_comment limit 1

2016-11-03 23:13:46.909   [9]  info   : (route_single_stmt): Route query to master      192.168.137.21:3306 <

2016-11-03 23:13:46.922   [9]  info   : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ, stmt: select USER()

2016-11-03 23:13:46.922   [9]  info   : (route_single_stmt): Route query to slave       192.168.137.22:3306 <

# 执行 SELECT * FROM test.t1 语句被路由到 192.168.137.22:3306[server2]中的日志

2016-11-03 23:15:02.618   [9]  info   : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ, stmt: SELECT * FROM test.t1

2016-11-03 23:15:02.618   [9]  info   : (route_single_stmt): Route query to slave       192.168.137.22:3306 <

# 执行 INSERT INTO test.t1 VALUES(NULL, ‘HH4‘, 4) 语句被路由到 192.168.137.21:3306[server1]中的日志

2016-11-03 23:17:02.716   [9]  info   : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_WRITE, stmt: INSERT INTO test.t1 VALUES(NULL, ‘HH4‘, 4)

2016-11-03 23:17:02.716   [9]  info   : (route_single_stmt): Route query to master      192.168.137.21:3306 <

上面是最基本的读写分离操作

重点参数说明与演示

有许多刚刚搭建Maxscale的朋友会问到为什么我的select总是落在Master上,影响比较大的参数有两个,如下:

# 监控主从复制延迟，可用后续指定router service的(配置此参数请求会永远落在 master)
detect_replication_lag=true

# 允许主从最大间隔(s).有些朋友在做压力测试的是会说SELECT 会打在Master,多半是这个参数
max_slave_replication_lag=3600

1

2

3

4

5

# 监控主从复制延迟，可用后续指定router service的(配置此参数请求会永远落在 master)

detect_replication_lag=true

# 允许主从最大间隔(s).有些朋友在做压力测试的是会说SELECT 会打在Master,多半是这个参数

max_slave_replication_lag=3600
  1. detect_replication_lag=true 时的现象

执行 SELECT 语句

HH@192.168.137.11 11:24:59 [(none)]>SELECT * FROM test.t1;
+----+------+-----+
| id | name | age |
+----+------+-----+
| 1 | HH1 | 1 |
| 2 | HH2 | 2 |
| 3 | HH3 | 3 |
| 4 | HH4 | 4 |
+----+------+-----+
4 rows in set (0.00 sec)

1

2

3

4

5

6

7

8

9

10

HH@192.168.137.11 11:24:59 [(none)]>SELECT * FROM test.t1;

+----+------+-----+

| id | name | age |

+----+------+-----+

|  1 | HH1  |   1 |

|  2 | HH2  |   2 |

|  3 | HH3  |   3 |

|  4 | HH4  |   4 |

+----+------+-----+

4 rows in set (0.00 sec)

查看路由的日志

# 该查询落在了Master(192.168.137.21:3306)[server1]上了
2016-11-03 23:25:04.364 [7] info : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ, stmt: SELECT * FROM test.t1
2016-11-03 23:25:04.364 [7] info : (route_single_stmt): Route query to master 192.168.137.21:3306 <

1

2

3

# 该查询落在了Master(192.168.137.21:3306)[server1]上了

2016-11-03 23:25:04.364   [7]  info   : (route_single_stmt): > Autocommit: [enabled], trx is [not open], cmd: COM_QUERY, type: QUERY_TYPE_READ, stmt: SELECT * FROM test.t1

2016-11-03 23:25:04.364   [7]  info   : (route_single_stmt): Route query to master      192.168.137.21:3306 <

所以我的配置是将 detect_replication_lag=true 给注释了也就是用默认值false.

关于 max_slave_replication_lag 这个参数我就不演示了, 因为涉及到了使用 sysbench 等压力工具不在本文范畴, 有兴趣的自己玩玩, 这边就说说该参数的意义。

如果主从延时大于该参数那么 QDL DML DDL 三种语句都落在 Master(192.168.137.21:3306)[server1]上。

昵称: HH

QQ: 275258836

ttlsa群交流沟通(QQ群②: 6690706 QQ群③: 168085569 QQ群④: 415230207（新） 微信公众号: ttlsacom)

感觉本文内容不错，读后有收获？

http://www.ttlsa.com/mysql/maxscale-install-read-write-split/

时间： 2024-10-24 04:29:26

Maxscale安装-读写分离(1)的相关文章

基于maxscale的读写分离部署笔记

使用maxscale搭建的读写分离架构,后期还可以再结合MHA做master的故障转移,这样业务层面上不需要做任何的改动即可. 基于connect方式的不要使用.从库延迟他还会继续分发请求过去,暂时不适合生产使用. 实验演示: 目前的主从结构: node93     10.1.20.93 master node94  10.1.20.94 slave node95  10.1.20.95 slave node96  10.1.20.96 maxscale 先在master主库上创建相关的账户:

MaxScale：实现MySQL读写分离与负载均衡的中间件利器

1.MaxScale 是干什么的? 配置好了MySQL的主从复制结构后,我们希望实现读写分离,把读操作分散到从服务器中,并且对多个从服务器能实现负载均衡. 读写分离和负载均衡是MySQL集群的基础需求,MaxScale 就可以帮着我们方便的实现这些功能. 2.MaxScale 的基础构成 MaxScale 是MySQL的兄弟公司 MariaDB 开发的,现在已经发展得非常成熟.MaxScale 是插件式结构,允许用户开发适合自己的插件. MaxScale 目前提供的插件功能分为5类: 认证插件

proxysql安装配置和读写分离初识

前言 笔者从事MySQL的相关工作,最近线上需要一款性能上佳的MySQL中间件产品,本人在了解一些如ProxySQL.MariaDB MaxScale.MySQL Router.Atlas.DBProxy等相关产品后,经过反复对比和相关测试,初步选用了proxysql.本文是proxysql系列的第一篇,笔者计划proxysql系列的博文将为您介绍proxysql的安装配置.读写分离.可用性测试.深入了解proxysql各组件.proxysql+keepalived实现高可用.proxysql和

maxscale配合MHA搭建读写分离的高可用架构（基于GTID replication主从架构，mysql5.6）

基于GTID的主从replication并配合MHA搭建高可用架构,请参考之前的博客:http://linzhijian.blog.51cto.com/1047212/1906434.这里只叙述如何在此基础上增加maxscale中间件,实现读写分离的功能. MaxScale是maridb开发的一个MySQL数据中间件,其配置简单,能够实现读写分离,并且可以根据主从状态实现写库的自动切换.官方文档:https://mariadb.com/kb/en/mariadb-enterprise/about

使用Maxscale实现mysql读写分离

MaxScale 是 MariaDB 的产品之一,可以很方便的实现读写分离方案:并且提供了读写分离的负载均衡和高可用性保障. 一.安装配置 前提:先配置好mysql的主从,Maxscale会根据主从复制信息来判断Master和slave 注:不能配置mysql互为主从,如果互为主从,两台都会被认为slave,在这种情况下,写请求会被拒绝,只接受读请求. 1.1.安装 官网下载对应的rpm包, wget  https://downloads.mariadb.com/MaxScale/2.0.3/c

maxscale读写分离

今天,写写mysql兄弟公司maridb开发的一个读写分离,既然是兄弟,那也适用于mysql. 1.安装依赖包 yum -y install gcc gcc-c++ ncurses ncurses-devel cmake 2.下载软件 cd /usr/local wget http://downloads.sourceforge.net/project/boost/boost/1.59.0/boost_1_59_0.tar.gz wget http://dev.mysql.com/get/Dow

Maxscale实现mysql的读写分离

1MaxScale 是干什么的? 配置好了MySQL的主从复制结构后,我们希望实现读写分离,把读操作分散到从服务器中,并且对多个从服务器能实现负载均衡. 读写分离和负载均衡是MySQL集群的基础需求,MaxScale 就可以帮着我们方便的实现这些功能. 2MaxScale 的基础构成 MaxScale 是MySQL的兄弟公司 MariaDB 开发的,现在已经发展得非常成熟.MaxScale 是插件式结构,允许用户开发适合自己的插件. MaxScale 目前提供的插件功能分为5类: 认证插件 提供

mysql-proxy源码安装及配置mysql读写分离

安装Mysql-proxy关联系统包 libevent libevent-devel glib2 glib2-devel lua 5.1.x lua-devel-5.1.x pkg-config mysql-devel openssl openssl-devel gcc* 2安装MySQL-proxy 0.8.5 下载源码包并解压 在源码包路径下安装 ./configure –prefix=/u01/mysql-proxy make make install 3.配置mysql-proxy.cn

实验2 安装Atlas实现读写分离

系统版本:        windows7x64 虚拟机:          centos 6.5x64 ip规划:          主数据库服务器:192.168.0.44 从数据库服务器:192.168.0.54 proxy服务器:192.168.0.29 ssh连接工具:    ssh secure shell client vpn工具:        ssl vpn-plus client 实验内容:        1.为proxy服务器下载安装Atlas 2.配置Atlas 3.运行