使用Amoeba让mysql主从服务器实现读写分离 / 憋错料

环境：

一台CentOS6.5-x64最小化安装(ip:10.0.0.226)

软件：jdk-8u60-linux-x64.rpm， amoeba-mysql-binary-2.2.0.tar.gz

下载地址：链接: http://pan.baidu.com/s/1c04Wmys 密码: 4tqe

2.一台CentOS6.5-x64最小化安装(ip:10.0.0.222)

为了节省资源，本次使用的是mysql多实例。3306为主(master)，3307为从（slave).

主从同步这里就不在说明了，创建好主从同步后要先停止从库同步。进入mysql后slave stop;

3.测试机（ip:10.0.0.111)

测试机应事先有装过mysql,不然登陆的amoeba服务器的时候会出现-bash: mysql: command not found.(如果不是这样的，还希望大侠能留下相关办法。谢谢！）

3306主库（master)创建用户,这个用户是用来给amoeba写数据时候使用。语句如下：

mysql> GRANT SELECT, INSERT, UPDATE, DELETE ON *.* TO ‘amoeba‘@‘10.0.0.%‘ IDENTIFIED BY ‘123456‘;

3307从库（slave)创建用户,这个用户是用来给amoeba查询数据时候使用。语句如下：

mysql> GRANT SELECT ON *.* TO ‘amoeba‘@‘10.0.0.%‘ IDENTIFIED BY ‘123456‘;

Amoeba安装和配置

安装：

[[email protected] ~]# rpm -ivh jdk-8u60-linux-x64.rpm

[[email protected] ~]# ln -s /usr/java/jdk1.8.0_60/ /usr/java/jdk1.8 #做个软连接，方便后面操作

[[email protected] ~]# vi /etc/profile

在最后面添加以下两行：

export JAVA_HOME=/usr/java/jdk1.8

export PATH=$JAVA_HOME/bin:$JAVA_HOME/jre/bin:$PATH

[[email protected] ~]# source /etc/profile #使刚加入的两行生效

[[email protected] ~]# mkdir -p /usr/local/amoeba

[[email protected] ~]# cd /usr/local/amoeba

[[email protected] amoeba]# tar xf amoeba-mysql-binary-2.2.0.tar.gz

[[email protected] amoeba]# rm amoeba-mysql-binary-2.2.0.tar.gz

[[email protected] amoeba]# chmod 700 -R bin/

配置：

2.2.0和1.3.1有些不一样

1.3.1是只要修改/usr/local/amoeba/conf/amoeba.xml这个配置文件就可以的

2.2.0是把/usr/local/amoeba/conf/amoeba.xml这个配置文件分开了，一个是amoeba.xml,另一个是dbServers.xml

下面贴出配置，尽供参考：

dbServers.xml

[[email protected] conf]# cat dbServers.xml

<?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

-->

<property name="manager">${defaultManager}</property>

<property name="user">amoeba</property>

</factoryConfig>

</poolConfig>

</dbServer>

<property name="manager">${defaultManager}</property>

<property name="user">amoeba</property>

</factoryConfig>

</poolConfig>

</dbServer>

</factoryConfig>

</dbServer>

</factoryConfig>

</dbServer>

<property name="poolNames">server1</property>

</poolConfig>

</dbServer>

<property name="poolNames">server2</property>

</poolConfig>

</dbServer>

</amoeba:dbServers>

amoeba.xml

[[email protected] conf]# cat amoeba.xml

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

<!DOCTYPE amoeba:configuration SYSTEM "amoeba.dtd">

<amoeba:configuration xmlns:amoeba="http://amoeba.meidusa.com/">

<proxy>

<property name="manager">${clientConnectioneManager}</property>

</bean>

</property>

<property name="ipFile">${amoeba.home}/conf/access_list.conf</property>

</bean>

</property>

</bean>

</property>

</service>

<!-- default value: random number

-->

<property name="manager">${clientConnectioneManager}</property>

</property>

</service>

</runtime>

</proxy>

<!--

Each ConnectionManager will start as thread

manager responsible for the Connection IO read , Death Detection

-->

<property name="subManagerClassName">com.meidusa.amoeba.net.ConnectionManager</property>

<!--

default value is avaliable Processors

-->

</connectionManager>

<property name="subManagerClassName">com.meidusa.amoeba.net.AuthingableConnectionManager</property>

<!--

default value is avaliable Processors

-->

</connectionManager>

</connectionManagerList>

<property name="configFile">${amoeba.home}/conf/dbServers.xml</property>

</dbServerLoader>

<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="defaultPool">master</property>

<property name="writePool">master</property>

<property name="readPool">slave</property>

</queryRouter>

</amoeba:configuration>

启动：

[[email protected] bin]# ./amoeba start

log4j:WARN log4j config load completed from file:/usr/local/amoeba/conf/log4j.xml

2015-10-20 21:12:18,932 INFO context.MysqlRuntimeContext - Amoeba for Mysql current versoin=5.1.45-mysql-amoeba-proxy-2.2.0

log4j:WARN ip access config load completed from file:/usr/local/amoeba/conf/access_list.conf

2015-10-20 21:12:19,593 INFO net.ServerableConnectionManager - Amoeba for Mysql listening on /10.0.0.226:8066.

2015-10-20 21:12:19,608 INFO net.ServerableConnectionManager - Amoeba Monitor Server listening on /10.0.0.226:17877.

[[email protected] bin]# netstat -lntp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 932/sshd

tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1008/master

tcp 0 0 ::ffff:10.0.0.226:17877 :::* LISTEN 1673/java

tcp 0 0 :::22 :::* LISTEN 932/sshd

tcp 0 0 ::1:25 :::* LISTEN 1008/master

tcp 0 0 ::ffff:10.0.0.226:8066 :::* LISTEN 1673/java

看到以上相关数据，说明已经起动成功。

===========================================================================================

验证：

为了能明显看出效果，这里先暂停主从同步。使用命令slave stop结束。

先进入主库3306[master]，查看测试数据库tudou的test表，内容如下

mysql> select * from test;

+--------+

| name |

+--------+

| shanqi |

+--------+

再进入从库3307[slave]，查看测试数据库tudou的test表，内容如下

mysql> select * from test;

+--------+

| name |

+--------+

| shanqi |

| green |

+--------+

这里已事先在从库插入一条主库没有的记录，方便接下来的测试。

使用一台测试机（IP：10.0.0.111）

登陆

[[email protected] amoeba]# mysql -uroot -p123456 -P8066 -h10.0.0.226

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

Your MySQL connection id is 1093642553

Server version: 5.1.45-mysql-amoeba-proxy-2.2.0 Source distribution

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.

mysql> show databases;

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

| Database |

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

| information_schema |

| ccmate |

| mysql |

| performance_schema |

| test |

| tudou |

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

6 rows in set (0.00 sec)

查询的时候，amoeba会自动去从库查询。

mysql> select * from tudou.test;

+--------+

| name |

+--------+

| shanqi |

| green |

+--------+

3 rows in set (0.01 sec)

插入一条记录到测试表tudou.test,然后去主库[master]查询下

mysql> insert into tudou.test values("test");

Query OK, 1 row affected (0.04 sec)

然后去主库[master]查询下

mysql> select * from test;

+--------+

| name |

+--------+

| shanqi |

| test |

+--------+

3 rows in set (0.00 sec)

到此说明amoeba读写分离成功。

问题：
启动的时候会出现以下问题：

[[email protected] bin]# ./amoeba start

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.

这里是amoeba 启动脚本判断时有个地方设置过小，需要修改下

[[email protected] bin]# vi amoeba

找到DEFAULT_OPTS="-server -Xms256m -Xmx256m -Xss128k"这一行，把128改成256即可

时间： 2024-10-15 07:16:37

使用Amoeba让mysql主从服务器实现读写分离

使用Amoeba让mysql主从服务器实现读写分离的相关文章

【纯干货】Amoeba实现MySQL主从同步与读写分离

CentOS 7上部署Amoeba实现MySQL主从同步，读写分离，负载均衡高可用群集

MySQL主从同步、读写分离配置步骤

MySQL主从同步、读写分离配置步骤、问题解决笔记

mysql主从同步、读写分离

MySQL主从复制技术与读写分离技术amoeba应用

mysql主从同步+mycat读写分离+.NET程序连接mycat代理

mysql主从配置，读写分离

DBA成长之路---mysql主从同步，读写分离