读写分离配置
本想采用Mysql Proxy来实现读写分离，奈何其使用的lua脚本着实让人头痛，最后决定采用国人开发的开源数据库代理中间件Amoeba。使用Amoeba，只需要简单的xml配置，就可以很容易地实现读写分离。
Amoeba处于应用程序和数据库服务器之间，充当一个中间代理层。其支持负载均衡、高可用性、Query过滤、读写分离、可路由相关的query到目标数据库、可并发请求多台数据库合并结果。功能很强大。
Amoeba默认的端口为8066，实现了Mysql协议。应用程序中只需要修改一个数据库连接就可以实现采用Amoeba来代理数据库访问。比如：java应用中，
假如你原来的jdbc连接字符串为：jdbc:mysql://192.168.168.42:3306/minishop，那么现在，你想
使用Amoeba作为数据库访问代理，则
只需要将上面连接字符串改为如下(假如Amoeba所在机子IP为192.168.168.88)：jdbc:mysql://192.168.168.88:8066/minishop。
Amoeba透明性做的很赞。
主要还是配置Amoeda，但是配置也是相当的简单。基本
只需要配置两个文件：
1.conf\dbServers.xml
2.conf\amoeba.xml。
配置中各项的含义，可以参考amoeda中文指南，这里不做过多解释。仅记录下配置。
dbServers.xml主要配置
[html] view plain copy
- <amoeba:dbServers xmlns:amoeba=“http://amoeba.meidusa.com/”>
-
- <property name=“port”>3306
property> -
- <property name=“schema”>minishop
property> -
- <property name=“user”>chenjie
property> -
- <property name=“password”>chenjie
property> -
factoryConfig> - <poolConfig class=“com.meidusa.amoeba.net.poolable.PoolableObjectPool”>
- <property name=“maxActive”>500
property> - <property name=“maxIdle”>500
property> - <property name=“minIdle”>10
property> - <property name=“minEvictableIdleTimeMillis”>
property> - <property name=“timeBetweenEvictionRunsMillis”>
property> - <property name=“testOnBorrow”>true
property> - <property name=“testWhileIdle”>true
property> -
poolConfig> -
dbServer> - <dbServer name=“master” parent=“abstractServer”>
- <factoryConfig>
-
- <property name=“ipAddress”>192.168.168.253
property> -
factoryConfig> -
dbServer> - <dbServer name=“slave1” parent=“abstractServer”>
- <factoryConfig>
-
- <property name=“ipAddress”>192.168.168.119
property> -
factoryConfig> -
dbServer> - <dbServer name=“slave2” parent=“abstractServer”>
- <factoryConfig>
-
- <property name=“ipAddress”>192.168.168.251
property> -
factoryConfig> -
dbServer> - <dbServer name=“multiPool” virtual=“true”>
- <poolConfig class=“com.meidusa.amoeba.server.MultipleServerPool”>
-
- <property name=“loadbalance”>1
property> -
- <property name=“poolNames”>slave1,slave2
property> -
poolConfig> -
dbServer> -
amoeba:dbServers>
amoeba.xml配置：
[html] view plain copy
- <amoeba:configuration xmlns:amoeba=“http://amoeba.meidusa.com/”>
- <proxy>
-
- <service name=“Amoeba for Mysql” class=“com.meidusa.amoeba.net.ServerableConnectionManager”>
-
- <property name=“port”>8066
property> -
- <property name=“ipAddress”>192.168.168.253
property> - <property name=“manager”>${clientConnectioneManager}
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=“authenticator”>
- <bean class=“com.meidusa.amoeba.mysql.server.MysqlClientAuthenticator”>
- <property name=“user”>chenjie
property> - <property name=“password”>chenjie
property> - <property name=“filter”>
- <bean class=“com.meidusa.amoeba.server.IPAccessController”>
- <property name=“ipFile”>${amoeba.home}/conf/access_list.conf
property> -
bean> -
property> -
bean> -
property> -
service> -
- <service name=“Amoeba Monitor Server” class=“com.meidusa.amoeba.monitor.MonitorServer”>
-
-
- <property name=“ipAddress”>127.0.0.1
property> - <property name=“daemon”>true
property> - <property name=“manager”>${clientConnectioneManager}
property> - <property name=“connectionFactory”>
- <bean class=“com.meidusa.amoeba.monitor.net.MonitorClientConnectionFactory”>
bean> -
property> -
service> - <runtime class=“com.meidusa.amoeba.mysql.context.MysqlRuntimeContext”>
-
- <property name=“readThreadPoolSize”>20
property> -
- <property name=“clientSideThreadPoolSize”>30
property> -
- <property name=“serverSideThreadPoolSize”>30
property> -
- <property name=“statementCacheSize”>500
property> -
- <property name=“queryTimeout”>60
property> -
runtime> -
proxy> -
- <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”>master
property> - <property name=“writePool”>master
property> - <property name=“readPool”>multiPool
property> - <property name=“needParse”>true
property> -
queryRouter> -
amoeba:configuration>
至此，Mysql主从热备和读写分离配置完毕。但是，具体应用到生产环境究竟如何，还有待测试和考察。后来测试一主多从，又加入了一台Mysql从数据库服务器，这就是为什么上面amoeba配置中多了一个IP为119的原因。
版权声明：本文内容由互联网用户自发贡献，该文观点仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请联系我们举报，一经查实，本站将立刻删除。
发布者：全栈程序员-站长，转载请注明出处：https://javaforall.net/220183.html原文链接：https://javaforall.net
