MySQL读写分离-Amoeba

1.下载amoebamysql

    https://pan.baidu.com/s/1qDV8pHAg9w7yDfnL7-Ew3gsql

2.上传amoebashell

    在xshell中使用rz -E命令便可上传文件数据库

    或者使用其余ftp/sftp工具上传app

3.安装amoeba负载均衡

    解压 tar -xf amoeba-mysql-3.0.4-BETA.tar.gz框架

4.配置dbServers.xmlide

    

<?xml version="1.0" encoding="gbk"?>

<!DOCTYPE amoeba:dbServers SYSTEM "dbserver.dtd">
<amoeba:dbServers xmlns:amoeba="http://amoeba.meidusa.com/">

	<!--
		<dbServer>是核心标签,用来配置物理数据库等
	-->
	
	<!-- abstractServer 是全部dbServer的父亲,就像Java中的继承,pom中的依赖;若是存在数据端口或者密码不一致,须要配置多个abstractServer -->
	<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>
			<!-- 数据库的端口号 -->
			<property name="port">3306</property>
			<!-- 数据库中的databaseId -->
			<property name="schema">test</property>
			<!-- 数据库用户名 -->
			<property name="user">root</property>
			<!-- 数据库密码 -->
			<property name="password">12340101</property>
		</factoryConfig>
		<!-- amoeba 维持的链接池,池中放的数据库链接 -->
		<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>

	<!-- 从数据库1配置 -->
	<dbServer name="slave1"  parent="abstractServer">
		<factoryConfig>
			<property name="ipAddress">192.168.245.112</property>
		</factoryConfig>
	</dbServer>
	<!-- 从数据库2配置 -->
	<dbServer name="master"  parent="abstractServer">
		<factoryConfig>
			<property name="ipAddress">192.168.245.111</property>
		</factoryConfig>
	</dbServer>
	<!-- 主数据库配置 -->
	<dbServer name="slave2"  parent="abstractServer">
		<factoryConfig>
			<property name="ipAddress">192.168.245.113</property>
		</factoryConfig>
	</dbServer>
	<!-- 一个数据库池,在读写分离中是关键,能够在amoeba.xml中指定读池为它,那么amoeba就会轮询里面的数据库,作到负载均衡 -->
	<dbServer name="multiPool" virtual="true">
		<poolConfig class="com.meidusa.amoeba.server.MultipleServerPool">
			<!--
				loadbalance=1 根据poolNames配置的dbServer进行轮询
				loadbalance=2 权重
				loadbalance=3 高可用
			-->
			<property name="loadbalance">1</property>
			<property name="poolNames">slave1,master,slave2</property>
		</poolConfig>
	</dbServer>
</amoeba:dbServers>

5.配置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">
			<!-- amoeba 监听的端口 ,程序链接的时候就要指定为该端口 -->
			<property name="port">8066</property>
			
			<!-- 绑定的IP -->
			<!-- 
			<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>
			
			
			<!-- 链接amoeba的用户名和密码,以及访问列表 -->
			<property name="authenticateProvider">
				<bean class="com.meidusa.amoeba.mysql.server.MysqlClientAuthenticator">
					
					<property name="user">root</property>
					
					<property name="password">12340101</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>
			
			<!-- 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>
		<!--
			重点在这里:
			writePool:修改操做走master数据库
			readPool :查询操做走multiPool数据库池
			defaultPool:若是没有配置writePool和readPool,就走它指定的数据库或者数据库池
		-->
		<property name="defaultPool">multiPool</property>
		<property name="writePool">master</property>
		<property name="readPool">multiPool</property>
		<property name="needParse">true</property>
	</queryRouter>
</amoeba:configuration>

6.启动amoeba.net

进入amoeba的bin目录

./launcher start &

去logs目录查看启动参数

ps -ef|grep launcher检查进程是否存在

netstat -an|grep 8066 检查端口是否处理监听状态

7.验证amoeba

打开Navicat,新建一个指向amoeba的链接,并打开数据库

amoeba优缺点

    优势:支持读写分离、分库分表、高可用

    缺点:高可用不稳定,分库分表支撑不好,稍微复杂的关联就不行了,开发团队也已经解散

读写分离开源框架发展过程:

    amoeba-cobar-mycat

amoeba已经被淘汰,开发团队也没有在维护,如今很流行mycat,它的读写分离、高可用、分库分表、数据库支撑比较全

MySQL读写分离-mycat

相关文章
相关标签/搜索