ProxySQL+Mysql實現數據庫讀寫分離實戰
ProxySQL介紹
ProxySQL是一個高性能的MySQL中間件，擁有強大的規則引擎。具備如下特性：http://www.proxysql.com/mysql
- 一、鏈接池，並且是multiplexing
- 二、主機和用戶的最大鏈接數限制
- 三、自動下線後端DB
延遲超過閥值
ping 延遲超過閥值
網絡不通或宕機 - 四、強大的規則路由引擎
實現讀寫分離
查詢重寫
sql流量鏡像 - 五、支持prepared statement
- 六、支持Query Cache
- 七、支持負載均衡，與gelera結合自動failover
總體環境介紹
一、系統環境
三臺服務器系統環境一致以下linux
[root@db1 ~]# cat /etc/redhat-release CentOS Linux release 7.4.1708 (Core) [root@db1 ~]# uname -r 3.10.0-693.el7.x86_64
二、IP地址與軟件版本git
proxy 192.168.22.171 db1 192.168.22.173 db2 192.168.22.174 mysql 5.7.17 proxy sql 1.4.8
三、關閉防火牆、selinuxgithub
systemctl stop firewalld #中止防火牆服務 systemctl disable firewalld #禁止開機自啓動 sed -i 's#SELINUX=enforcing#SELINUX=disabled#g' /etc/selinux/conf && reboot #用sed命令替換的試修改selinux的配置文件
四、mysql安裝與主從同步
安裝請參考如下文章
LAMP架構應用實戰——MySQL服務sql
主從同步請參如下文章數據庫
安裝佈署過程
一、數據庫主從同步centos
查看主從同步狀態
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.22.173
Master_User: rep
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master-log.000001
Read_Master_Log_Pos: 154
Relay_Log_File: db2-relay-bin.000002
Relay_Log_Pos: 321
Relay_Master_Log_File: master-log.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: 526
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: 1
Master_UUID: 70a61633-63ae-11e8-ab86-000c29fe99ea
Master_Info_File: /mysqldata/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: 0
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)
檢測主從同步服務器
[root@db1 ~]# mysql -uroot -p -e "create database testdb;" Enter password: [root@db1 ~]# mysql -uroot -p -e "show databases;" |grep testdb Enter password: testdb #db2上查看是否同步 mysql> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | sys | | testdb | +--------------------+ 5 rows in set (0.01 sec)
二、準備proxySQL軟件網絡
[root@proxy ~]# wget https://github.com/sysown/proxysql/releases/download/v1.4.8/proxysql-1.4.8-1-centos7.x86_64.rpm [root@proxy ~]# ll proxysql-1.4.8-1-centos7.x86_64.rpm -rw-r--r-- 1 root root 5977168 Apr 10 11:38 proxysql-1.4.8-1-centos7.x86_64.rpm
三、安裝配置
[root@proxy ~]# yum install -y proxysql-1.4.8-1-centos7.x86_64.rpm [root@proxy ~]# rpm -ql proxysql /etc/init.d/proxysql #啓動腳本 /etc/proxysql.cnf #配置文件，僅在第一次(/var/lib/proxysql/proxysql.db文件不存在)啓動時有效。啓#動後能夠在proxysql管理端中經過修改數據庫的方式修改配置並生效(官方推薦方式。) /usr/bin/proxysql #主程序文件 /usr/share/proxysql/tools/proxysql_galera_checker.sh /usr/share/proxysql/tools/proxysql_galera_writer.pl
四、配置文件詳解
[root@proxy ~]# egrep -v "^#|^$" /etc/proxysql.cnf
datadir="/var/lib/proxysql" #數據目錄
admin_variables=
{
admin_credentials="admin:admin" #鏈接管理端的用戶名與密碼
mysql_ifaces="0.0.0.0:6032" #管理端口，用來鏈接proxysql的管理數據庫
}
mysql_variables=
{
threads=4 #指定轉發端口開啓的線程數量
max_connections=2048
default_query_delay=0
default_query_timeout=36000000
have_compress=true
poll_timeout=2000
interfaces="0.0.0.0:6033" #指定轉發端口，用於鏈接後端mysql數據庫的，至關於代理做用
default_schema="information_schema"
stacksize=1048576
server_version="5.5.30" #指定後端mysql的版本
connect_timeout_server=3000
monitor_username="monitor"
monitor_password="monitor"
monitor_history=600000
monitor_connect_interval=60000
monitor_ping_interval=10000
monitor_read_only_interval=1500
monitor_read_only_timeout=500
ping_interval_server_msec=120000
ping_timeout_server=500
commands_stats=true
sessions_sort=true
connect_retries_on_failure=10
}
mysql_servers =
(
)
mysql_users:
(
)
mysql_query_rules:
(
)
scheduler=
(
)
mysql_replication_hostgroups=
(
)
#所以咱們使用官方推薦的方式來配置proxy sql
五、啓動服務並查看
[root@proxy ~]# /etc/init.d/proxysql start
Starting ProxySQL: DONE!
[root@proxy ~]# ss -lntup|grep proxy
tcp LISTEN 0 128 *:6032 *:* users:(("proxysql",pid=1199,fd=23))
tcp LISTEN 0 128 *:6033 *:* users:(("proxysql",pid=1199,fd=22))
tcp LISTEN 0 128 *:6033 *:* users:(("proxysql",pid=1199,fd=21))
tcp LISTEN 0 128 *:6033 *:* users:(("proxysql",pid=1199,fd=20))
tcp LISTEN 0 128 *:6033 *:* users:(("proxysql",pid=1199,fd=19))
#能夠看出轉發端口6033是啓動了四個線程
六、在mysql上配置帳號並受權
mysql> GRANT ALL ON *.* TO 'proxysql'@'192.168.22.%' IDENTIFIED BY '123456'; Query OK, 0 rows affected, 1 warning (0.03 sec) mysql> flush privileges; Query OK, 0 rows affected (0.02 sec)
七、proxysql默認數據庫說明
[root@proxy ~]# yum install mysql -y [root@proxy ~]# mysql -uadmin -padmin -h127.0.0.1 -P6032 Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.5.30 (ProxySQL Admin Module) Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MySQL [(none)]> show databases; +-----+---------------+-------------------------------------+ | seq | name | file | +-----+---------------+-------------------------------------+ | 0 | main | | | 2 | disk | /var/lib/proxysql/proxysql.db | | 3 | stats | | | 4 | monitor | | | 5 | stats_history | /var/lib/proxysql/proxysql_stats.db | +-----+---------------+-------------------------------------+ 5 rows in set (0.00 sec) main：內存配置數據庫，表裏存放後端db實例、用戶驗證、路由規則等信息。表名以 runtime_開頭的表示proxysql當前運行的配置內容，不能經過dml語句修改，只能修改對應的不以 runtime_ 開頭的（在內存）裏的表，而後 LOAD 使其生效， SAVE 使其存到硬盤以供下次重啓加載。 disk：是持久化到硬盤的配置，sqlite數據文件。 stats：是proxysql運行抓取的統計信息，包括到後端各命令的執行次數、流量、processlist、查詢種類彙總/執行時間等等。 monitor：庫存儲 monitor 模塊收集的信息，主要是對後端db的健康/延遲檢查。
八、proxysql的配置系統
ProxySQL具備一個複雜但易於使用的配置系統，能夠知足如下需求：
- 一、容許輕鬆動態更新配置（這是爲了讓ProxySQL用戶能夠在須要零宕機時間配置的大型基礎架構中使用它）。與MySQL兼容的管理界面可用於此目的。
- 二、容許儘量多的配置項目動態修改，而不須要從新啓動ProxySQL進程
- 三、能夠絕不費力地回滾無效配置
- 四、這是經過多級配置系統實現的，其中設置從運行時移到內存，並根據須要持久保存到磁盤。
3級配置由如下幾層組成：
+-------------------------+
| RUNTIME |
+-------------------------+
/|\ |
| |
[1] | [2] |
| \|/
+-------------------------+
| MEMORY |
+-------------------------+ _
/|\ | |\
| | \
[3] | [4] | \ [5]
| \|/ \
+-------------------------+ +-------------------------+
| DISK | | CONFIG FILE |
+-------------------------+ +-------------------------+
參考文章：https://github.com/sysown/proxysql/wiki/Configuring-ProxySQL
九、配置proxysql管理用戶
proxysql默認的表信息以下
MySQL [main]> show tables;
+--------------------------------------------+
| tables |
+--------------------------------------------+
| global_variables |
| mysql_collations |
| mysql_group_replication_hostgroups |
| mysql_query_rules |
| mysql_query_rules_fast_routing |
| mysql_replication_hostgroups |
| mysql_servers |
| mysql_users |
| proxysql_servers |
| runtime_checksums_values |
| runtime_global_variables |
| runtime_mysql_group_replication_hostgroups |
| runtime_mysql_query_rules |
| runtime_mysql_query_rules_fast_routing |
| runtime_mysql_replication_hostgroups |
| runtime_mysql_servers |
| runtime_mysql_users |
| runtime_proxysql_servers |
| runtime_scheduler |
| scheduler |
+--------------------------------------------+
20 rows in set (0.00 sec)
#這裏是使用insert into語句來動態配置，而能夠不須要重啓
MySQL [(none)]> insert into mysql_servers(hostgroup_id,hostname,port,weight,comment) values(1,'db1','3306',1,'Write Group');
Query OK, 1 row affected (0.01 sec)
MySQL [(none)]> insert into mysql_servers(hostgroup_id,hostname,port,weight,comment) values(2,'db2','3307',1,'Read Group');
Query OK, 1 row affected (0.00 sec)
MySQL [(none)]> select * from mysql_servers;
+--------------+----------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+-------------+
| hostgroup_id | hostname | port | status | weight | compression | max_connections | max_replication_lag | use_ssl | max_latency_ms | comment |
+--------------+----------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+-------------+
| 1 | db1 | 3306 | ONLINE | 1 | 0 | 1000 | 0 | 0 | 0 | Write Group |
| 2 | db2 | 3307 | ONLINE | 1 | 0 | 1000 | 0 | 0 | 0 | Read Group |
+--------------+----------+------+--------+--------+-------------+-----------------+---------------------+---------+----------------+-------------+
2 rows in set (0.00 sec)
#接下來將剛剛在mysql客戶端建立的用戶寫入到proxy sql主機的mysql_users表中，它也是用於proxysql客戶端訪問數據庫，默認組是寫組，當讀寫分離規則出現問題時，它會直接訪問默認組的數據庫。
MySQL [main]> INSERT INTO mysql_users(username,password,default_hostgroup) VALUES ('proxysql','123456',1);
Query OK, 1 row affected (0.00 sec)
MySQL [main]> select * from mysql_users;
+----------+----------+--------+---------+-------------------+----------------+---------------+------------------------+--------------+---------+----------+-----------------+
| username | password | active | use_ssl | default_hostgroup | default_schema | schema_locked | transaction_persistent | fast_forward | backend | frontend | max_connections |
+----------+----------+--------+---------+-------------------+----------------+---------------+------------------------+--------------+---------+----------+-----------------+
| proxysql | 123456 | 1 | 0 | 1 | NULL | 0 | 1 | 0 | 1 | 1 | 10000 |
+----------+----------+--------+---------+-------------------+----------------+---------------+------------------------+--------------+---------+----------+-----------------+
1 row in set (0.00 sec)
在mysql上添加監控的用戶
mysql> GRANT SELECT ON *.* TO 'monitor'@'192.168.22.%' IDENTIFIED BY 'monitor';
Query OK, 0 rows affected, 1 warning (0.00 sec)
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)
#在proxysql主機端配置監控用戶
MySQL [main]> set mysql-monitor_username='monitor';
Query OK, 1 row affected (0.00 sec)
MySQL [main]> set mysql-monitor_password='monitor';
Query OK, 1 row affected (0.00 sec)
#參考文章：https://github.com/sysown/proxysql/wiki/ProxySQL-Configuration
十、配置proxysql的轉發規則
MySQL [main]> insert into mysql_query_rules(rule_id,active,match_digest,destination_hostgroup,apply)values(1,1,'^SELECT.*FOR UPDATE$',1,1); Query OK, 1 row affected (0.01 sec) MySQL [main]> insert into mysql_query_rules(rule_id,active,match_digest,destination_hostgroup,apply)values(2,1,'^SELECT',2,1); Query OK, 1 row affected (0.00 sec) MySQL [main]> select rule_id,active,match_digest,destination_hostgroup,apply from mysql_query_rules; +---------+--------+----------------------+-----------------------+-------+ | rule_id | active | match_digest | destination_hostgroup | apply | +---------+--------+----------------------+-----------------------+-------+ | 1 | 1 | ^SELECT.*FOR UPDATE$ | 1 | 1 | | 2 | 1 | ^SELECT | 2 | 1 | +---------+--------+----------------------+-----------------------+-------+ 2 rows in set (0.00 sec) #配置查詢select的請求轉發到hostgroup_id=2組上（讀組） #徵對select * from table_name for update這樣的修改語句，咱們是須要將請求轉到寫組，也就是hostgroup_id=1 #對於其它沒有被規則匹配的請求所有轉發到默認的組（mysql_users表中default_hostgroup）
十一、更新配置到RUNTIME中
由上面的配置系統層級關係能夠得知全部進來的請求首先是通過RUNTIME層
MySQL [main]> load mysql users to runtime; Query OK, 0 rows affected (0.00 sec) MySQL [main]> load mysql servers to runtime; Query OK, 0 rows affected (0.02 sec) MySQL [main]> load mysql query rules to runtime; Query OK, 0 rows affected (0.00 sec) MySQL [main]> load mysql variables to runtime; Query OK, 0 rows affected (0.00 sec) MySQL [main]> load admin variables to runtime; Query OK, 0 rows affected (0.00 sec)
十二、將全部配置保存至磁盤上
全部配置數據保存到磁盤上，也就是永久寫入/var/lib/proxysql/proxysql.db這個文件中
MySQL [main]> save mysql users to disk; Query OK, 0 rows affected (0.03 sec) MySQL [main]> save mysql servers to disk; Query OK, 0 rows affected (0.04 sec) MySQL [main]> save mysql query rules to disk; Query OK, 0 rows affected (0.03 sec) MySQL [main]> save mysql variables to disk; Query OK, 94 rows affected (0.02 sec) MySQL [main]> save admin variables to disk; Query OK, 31 rows affected (0.02 sec) MySQL [main]> load mysql users to runtime; Query OK, 0 rows affected (0.00 sec)
1三、測試讀寫分離
[root@proxy ~]# mysql -uproxysql -p123456 -h 127.0.0.1 -P 6033
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.5.30 (ProxySQL)
Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MySQL [(none)]> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sys |
| testdb |
+--------------------+
5 rows in set (0.02 sec)
#這纔是咱們真正的數據庫啊
建立數據與表，測試讀寫分離狀況
MySQL [(none)]> create database test_proxysql;
Query OK, 1 row affected (0.02 sec)
MySQL [(none)]> use test_proxysql;
Database changed
MySQL [test_proxysql]> create table test_tables(name varchar(20),age int(4));
Query OK, 0 rows affected (0.07 sec)
MySQL [test_proxysql]> insert into test_tables values('zhao','30');
Query OK, 1 row affected (0.09 sec)
MySQL [test_proxysql]> select * from test_tables;
+------+------+
| name | age |
+------+------+
| zhao | 30 |
+------+------+
1 row in set (0.02 sec)
在proxysql管理端查看讀寫分離
MySQL [main]> select * from stats_mysql_query_digest;
+-----------+--------------------+----------+--------------------+------------------------------------------------------+------------+------------+------------+----------+----------+----------+
| hostgroup | schemaname | username | digest | digest_text | count_star | first_seen | last_seen | sum_time | min_time | max_time |
+-----------+--------------------+----------+--------------------+------------------------------------------------------+------------+------------+------------+----------+----------+----------+
| 2 | test_proxysql | proxysql | 0x57CF7EC26C91DF9A | select * from test_tables | 1 | 1527667635 | 1527667635 | 14253 | 14253 | 14253 |
| 1 | information_schema | proxysql | 0x226CD90D52A2BA0B | select @@version_comment limit ? | 1 | 1527667214 | 1527667214 | 0 | 0 | 0 |
| 1 | test_proxysql | proxysql | 0xFF9877421CFBDA6F | insert into test_tables values(?,?) | 1 | 1527667623 | 1527667623 | 89033 | 89033 | 89033 |
| 1 | information_schema | proxysql | 0xE662AE2DEE853B44 | create database test-proxysql | 1 | 1527667316 | 1527667316 | 8470 | 8470 | 8470 |
| 1 | information_schema | proxysql | 0x02033E45904D3DF0 | show databases | 1 | 1527667222 | 1527667222 | 19414 | 19414 | 19414 |
| 1 | information_schema | proxysql | 0xB9EF28C84E4207EC | create database test_proxysql | 1 | 1527667332 | 1527667332 | 15814 | 15814 | 15814 |
| 2 | information_schema | proxysql | 0x620B328FE9D6D71A | SELECT DATABASE() | 1 | 1527667342 | 1527667342 | 23386 | 23386 | 23386 |
| 1 | test_proxysql | proxysql | 0x02033E45904D3DF0 | show databases | 1 | 1527667342 | 1527667342 | 2451 | 2451 | 2451 |
| 1 | test_proxysql | proxysql | 0x59F02DA280268525 | create table test_tables | 1 | 1527667360 | 1527667360 | 9187 | 9187 | 9187 |
| 1 | test_proxysql | proxysql | 0x99531AEFF718C501 | show tables | 1 | 1527667342 | 1527667342 | 1001 | 1001 | 1001 |
| 1 | test_proxysql | proxysql | 0xC745E37AAF6095AF | create table test_tables(name varchar(?),age int(?)) | 1 | 1527667558 | 1527667558 | 68935 | 68935 | 68935 |
+-----------+--------------------+----------+--------------------+------------------------------------------------------+------------+------------+------------+----------+----------+----------+
11 rows in set (0.01 sec)
#從上述結果就能夠看出讀寫分離配置是成功的，讀請求是轉發到2組，寫請求轉發到1組
整個讀寫分離的架構配置到此就完成了，可是此架構存在須要優化的地方，那就是此架構存在單點問題。實際生產環境中可採用MHA+ProxySQL+Mysql這類架構解決此問題，請持續關注【民工哥技術之路】公衆號，後續輸出相關的架構實戰。
關於Mysql各種高可用架構可閱讀前面的文章
淺談MySQL集羣高可用架構
MySQL集羣高可用架構之MHA
Mysql+Mycat實現數據庫主從同步與讀寫分離
版權申明：©著做權歸做者全部：來自做者民工哥的原創做品，如需轉載，請註明出處，不然將追究法律責任
相關文章
- 1. Spring 實現數據庫讀寫分離
- 2. spring實現數據庫讀寫分離
- 3. mysql數據庫實現讀寫分離
- 4. ProxySQL+Mysql實現數據庫讀寫分離實戰
- 5. mycat實現讀寫分離,實現數據庫負載均衡
- 6. 用MyCat實現數據庫讀寫分離與分庫分表
- 7. Django實現數據庫讀寫分離、一主多從、分庫
- 8. Spring 配置多數據源實現數據庫讀寫分離
- 9. Spring配置多數據源實現數據庫讀寫分離
- 10. mysql的讀寫分離 laravel實現數據庫讀寫分離配置或者多讀寫分離配置
- 更多相關文章...
- • SQLite 分離數據庫 - SQLite教程
- • AJAX 數據庫實例 - ASP 教程
- • Docker容器實戰(六) - 容器的隔離與限制
- • Spring Cloud 微服務實戰(三) - 服務註冊與發現
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
