Mysql 實戰之——生產環境讀寫分離方案
Linux環境：Centos 6.8 64-bit
Mysql 版本：5.1.7
1、準備工做：部署Mysql主從複製
2、使用Amoeba數據庫代理來實現讀寫分離
Amoeba做爲數據庫代理，以中間件的形式存在，拓撲圖以下所示：（Amoeba官網的一張圖）mysql
一、下載Amoeba：https://sourceforge.net/projects/amoeba/files/linux
二、解壓並複製到local目錄sql
[root@ linux ~]# unzip amoeba-mysql-3.0.5-RC-distribution.zip [root@ linux ~]# cp -rf amoeba-mysql-3.0.5-RC /usr/local
三、啓動Amoeba。數據庫
[root@chenllcentos ~]# /usr/local/amoeba-mysql-3.0.5-RC/bin/launcher
若是出現fatal exception：centos
The stack size specified is too small, Specify at least 228k Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
緣由是因爲stack size過小，致使JVM啓動失敗，要如何修改呢？bash
解決：服務器
[root@ linux ~]# vi /usr/local/amoeba-mysql-3.0.5-RC/jvm.properties
將內容：app
JVM_OPTIONS="-server -Xms256m -Xmx1024m -Xss196k -XX:PermSize=16m -XX:MaxPermSize=96m"
替換爲：jvm
JVM_OPTIONS="-server -Xms1024m -Xmx1024m -Xss256k -XX:PermSize=16m -XX:MaxPermSize=96m"
四、修改配置文件：Amoeba完成讀寫分離的實現主要是依靠2個很是重要的配置文件：ide
dbServers.xml 和 amoeba.xml
4.一、首先，看看dbServers.xml文件
[root@localhost conf]# cat dbServer.xml
這個文件主要是配置數據庫連接，主庫，還有從庫（slave）節點的信息，以及數據庫鏈接池信息
以下內容就是這個文件的配置
<?xml version="1.0" encoding="gbk"?>
<!DOCTYPE amoeba:dbServers SYSTEM 「dbserver.dtd」> <amoeba:dbServers xmlns:amoeba=「http://amoeba.meidusa.com/」>
<!--
Each dbServer needs to be configured into a Pool,
If you need to configure multiple dbServer with load balancing that can be simplified by the following configuration:
add attribute with name virtual = "true" in dbServer, but the configuration does not allow the element with name factoryConfig
such as 'multiPool' dbServer
-->
<!-- 該dbServer節點abstractive="true"，包含Mysql的公共配置信息，其餘dbServer節點都繼承該節點 -->
<!-- 設置節點配置的繼承結構，能夠避免重複配置相同信息，減小配置文件冗餘 -->
<dbServer name="abstractServer" abstractive="true">
<factoryConfig class="com.meidusa.amoeba.mysql.net.MysqlServerConnectionFactory">
<property name="connectionManager">${defaultManager}</property>
<property name="sendBufferSize">64</property>
<property name="receiveBufferSize">128</property>
<!-- mysql port -->
<!-- Mysql默認端口 -->
<property name="port">3306</property>
<!-- mysql schema -->
<!-- 默認鏈接的數據庫，若不存在須要事先建立，不然Amoeba啓動報錯 -->
<property name="schema">testdb</property>
<!-- mysql user -->
<property name="user">root</property>
<property name="password">222</property>
</factoryConfig>
<poolConfig class="com.meidusa.toolkit.common.poolable.PoolableObjectPool">
<property name="maxActive">500</property>
<property name="maxIdle">500</property>
<property name="minIdle">1</property>
<property name="minEvictableIdleTimeMillis">600000</property>
<property name="timeBetweenEvictionRunsMillis">600000</property>
<property name="testOnBorrow">true</property>
<property name="testOnReturn">true</property>
<property name="testWhileIdle">true</property>
</poolConfig>
</dbServer>
<!-- Mysql主服務器master節點繼承abstractServer -->
<dbServer name="master" parent="abstractServer">
<factoryConfig>
<!-- master數據庫主機地址 -->
<property name="ipAddress">192.168.48.133</property>
</factoryConfig>
</dbServer>
<!-- Mysql從服務器slave節點繼承abstractServer -->
<dbServer name="slave1" parent="abstractServer">
<factoryConfig>
<!-- slave數據庫主機地址 -->
<property name="ipAddress">192.168.48.132</property>
</factoryConfig>
</dbServer>
<!-- 若是有多個從服務器節點, 能夠複製多個dbServer -->
<!-- 配置數據庫讀取鏈接池 Amoeba實現讀寫分離根據readPool 鏈接池來實現-->
<dbServer name="readPool" virtual="true">
<poolConfig class="com.meidusa.amoeba.server.MultipleServerPool">
<!-- Load balancing strategy: 1=ROUNDROBIN , 2=WEIGHTBASED , 3=HA-->
<property name="loadbalance">1</property>
<!-- Separated by commas,such as: server1,server2,server1 -->
<property name="poolNames">slave1</property>
</poolConfig>
</dbServer>
配置完成以後：
4.二、接着配置amoeba.xml
vi amoeba.xml
內容以下：
<?xml version="1.0" encoding="gbk"?>
<!DOCTYPE amoeba:configuration SYSTEM "amoeba.dtd">
<amoeba:configuration xmlns:amoeba="http://amoeba.meidusa.com/">
<proxy>
<!-- service class must implements com.meidusa.amoeba.service.Service -->
<service name="Amoeba for Mysql" class="com.meidusa.amoeba.mysql.server.MySQLService">
<!-- port -->
<property name="port">8066</property>
<!-- bind ipAddress -->
<!--
<property name="ipAddress">127.0.0.1</property>
-->
<property name="connectionFactory">
<bean class="com.meidusa.amoeba.mysql.net.MysqlClientConnectionFactory">
<property name="sendBufferSize">128</property>
<property name="receiveBufferSize">64</property>
</bean>
</property>
<property name="authenticateProvider">
<bean class="com.meidusa.amoeba.mysql.server.MysqlClientAuthenticator">
<property name="user">root</property>
<property name="password"></property>
<property name="filter">
<bean class="com.meidusa.toolkit.net.authenticate.server.IPAccessController">
<property name="ipFile">${amoeba.home}/conf/access_list.conf</property>
</bean>
</property>
</bean>
</property>
</service>
<runtime class="com.meidusa.amoeba.mysql.context.MysqlRuntimeContext">
<!-- proxy server client process thread size -->
<property name="executeThreadSize">128</property>
<!-- per connection cache prepared statement size -->
<property name="statementCacheSize">500</property>
<!-- default charset -->
<property name="serverCharset">utf8</property>
<!-- query timeout( default: 60 second , TimeUnit:second) -->
<property name="queryTimeout">60</property>
</runtime>
</proxy>
<!--
Each ConnectionManager will start as thread
manager responsible for the Connection IO read , Death Detection
-->
<connectionManagerList>
<connectionManager name="defaultManager" class="com.meidusa.toolkit.net.MultiConnectionManagerWrapper">
<property name="subManagerClassName">com.meidusa.toolkit.net.AuthingableConnectionManager</property>
</connectionManager>
</connectionManagerList>
<!-- default using file loader -->
<dbServerLoader class="com.meidusa.amoeba.context.DBServerConfigFileLoader">
<property name="configFile">${amoeba.home}/conf/dbServers.xml</property>
</dbServerLoader>
<queryRouter class="com.meidusa.amoeba.mysql.parser.MysqlQueryRouter">
<property name="ruleLoader">
<bean class="com.meidusa.amoeba.route.TableRuleFileLoader">
<property name="ruleFile">${amoeba.home}/conf/rule.xml</property>
<property name="functionFile">${amoeba.home}/conf/ruleFunctionMap.xml</property>
</bean>
</property>
<property name="sqlFunctionFile">${amoeba.home}/conf/functionMap.xml</property>
<property name="LRUMapSize">1500</property>
<property name="defaultPool">multiPool</property>
<!--
<property name="writePool">server1</property>
<property name="readPool">server1</property>
-->
<property name="needParse">true</property>
</queryRouter>
</amoeba:configuration>
咱們須要改的有3個地方：
五、啓動
cd /usr/local/amoeba-mysql-3.0.5-RC/bin/ ./launcher
出現以下信息就是啓動成功了
2016-10-11 23:20:55 [INFO] Project Name=Amoeba-MySQL, PID=4097 , System shutdown .... 2016-10-11 23:27:49 [INFO] Project Name=Amoeba-MySQL, PID=4162 , starting... log4j:WARN log4j config load completed from file:/usr/local/amoeba-mysql-3.0.5-RC/conf/log4j.xml 2016-10-11 23:27:50,736 INFO context.MysqlRuntimeContext - Amoeba for Mysql current versoin=5.1.45-mysql-amoeba-proxy-3.0.4-BETA log4j:WARN ip access config load completed from file:/usr/local/amoeba-mysql-3.0.5-RC/conf/access_list.conf 2016-10-11 23:27:51,863 INFO net.ServerableConnectionManager - Server listening on 0.0.0.0/0.0.0.0:8066.
六、測試
先中止從庫的主從複製
mysql>slave stop;
查詢主庫的數據
mysql> select * from t_test; +------+------+ | id | name | +------+------+ | 3 | t3 | +------+------+
查詢從庫的數據
mysql> select * from t_test; +------+------+ | id | name | +------+------+ | 1 | aaa | +------+------+
登陸Amoeba
mysql -uroot -p111111 -h192.168.48.133 -P8066
先使用查詢語句
-- 通過屢次測試查詢，始終返回從庫的數據 mysql> select * from t_test ; +------+------+ | id | name | +------+------+ | 1 | aaa | +------+------+ 1 row in set (0.00 sec)
再使用insert語句
mysql> insert into t_test (id,name) values (100,'100'); Query OK, 1 row affected (0.02 sec) mysql> insert into t_test (id,name) values (200,'200'); Query OK, 1 row affected (0.00 sec)
如今看看insert語句的結果：
-- 查詢從庫的結果： mysql> select * from t_test; +------+------+ | id | name | +------+------+ | 100 | 100 | | 200 | 200 | +------+------+
-- 查詢主庫的結果 mysql> select * from t_test; +------+------+ | id | name | +------+------+ | 200 | 200 | | 100 | 100 | +------+------+ 2 rows in set (0.00 sec)
--在Amoeba執行查詢的結果： mysql> select * from t_test ; +------+------+ | id | name | +------+------+ | 100 | 100 | | 200 | 200 | +------+------+ 2 rows in set (0.07 sec)
已經成功了。。。查詢操做，始終查詢的是從庫的數據，而insert操做，始終是對主庫進行操做
JAVA程序中整合amoeba的話，只須要把數據庫連接改爲amoeba的就好了。。
在企業的實際項目中，這樣作的好處是，不須要對代碼進行硬編碼，具有很是高的解耦做用，並且，Amoeba的配置也很是的簡單，其實還有分庫和分表的操做，這裏就不作演示
3、報錯信息
amoeba裏查詢的時候報錯： amoeba ERROR 1044 (42000): Could not create a validated object, cause: ValidateObject failed
這個問題，我在網上找到了一個緣由，就是，amoeba去從庫查詢的時候，帳號沒權限。grant 賦予從庫那個帳號全部權限就行了。
相關文章
- 1. 生產環境實踐Mysql5.7主從+Atlas實現讀寫分離
- 2. Mysql讀寫分離方案－MySQL Proxy環境部署記錄
- 3. MySQL 讀寫分離方案－MySQL Proxy環境部署記錄
- 4. Mysql讀寫分離方案－Amoeba環境部署記錄
- 5. docker環境 mysql讀寫分離 mycat maxscale
- 6. window環境下mysql讀寫分離
- 7. Mycat生產實踐---Mycat讀寫分離案例
- 8. springboot環境下實現讀寫分離
- 9. PHP+MYSQL 讀寫分離簡單實戰
- 10. SpringBoot + MyBatis + MySQL 讀寫分離實戰
- 更多相關文章...
- • C# 環境 - C#教程
- • SQLite 分離數據庫 - SQLite教程
- • 常用的分佈式事務解決方案
- • Docker容器實戰(六) - 容器的隔離與限制
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
相關文章