Amoeba：读写分离

最新推荐文章于 2024-09-01 15:30:33 发布
最新推荐文章于 2024-09-01 15:30:33 发布
阅读量112 收藏
点赞数
文章标签： java 数据库 runtime
1、安装jdk
  1. root@proxy:~# java -version
  2. java version "1.6.0_45"
  3. Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
  4. Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
2、配置dbServer.xml
  1. root@proxy:/usr/local/amoeba/conf# cat dbServers.xml
  2. <?xml version="1.0" encoding="gbk"?>

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

  7.                 <!--
  8.                         Each dbServer needs to be configured into a Pool,
  9.                         If you need to configure multiple dbServer with load balancing that can be simplified by the following configuration:
  10.                          add attribute with name virtual = "true" in dbServer, but the configuration does not allow the element with name factoryConfig
  11.                          such as 'multiPool' dbServer
  12.                 -->

  14.         <dbServer name="abstractServer" abstractive="true">
  15.                 <factoryConfig class="com.meidusa.amoeba.mysql.net.MysqlServerConnectionFactory">
  16.                         <property name="manager">${defaultManager}</property>
  17.                         <property name="sendBufferSize">64</property>
  18.                         <property name="receiveBufferSize">128</property>

  20.                         <!-- mysql port -->
  21.                         <property name="port">3306</property>

  23.                         <!-- mysql schema -->
  24.                         <property name="schema">test</property>

  26.                         <!-- mysql user -->
  27.                         <property name="user">root</property>

  29.                         <!-- mysql password -->
  30.                         <property name="password">111</property>

  32.                 </factoryConfig>

  34.                 <poolConfig class="com.meidusa.amoeba.net.poolable.PoolableObjectPool">
  35.                         <property name="maxActive">500</property>
  36.                         <property name="maxIdle">500</property>
  37.                         <property name="minIdle">10</property>
  38.                         <property name="minEvictableIdleTimeMillis">600000</property>
  39.                         <property name="timeBetweenEvictionRunsMillis">600000</property>
  40.                         <property name="testOnBorrow">true</property>
  41.                         <property name="testOnReturn">true</property>
  42.                         <property name="testWhileIdle">true</property>
  43.                 </poolConfig>
  44.         </dbServer>

  46.         <dbServer name="master1" parent="abstractServer">
  47.                 <factoryConfig>
  48.                         <!-- mysql ip -->
  49.                         <property name="ipAddress">10.10.10.40</property>
  50.                 </factoryConfig>
  51.         </dbServer>

  53.         <dbServer name="master2" parent="abstractServer">
  54.                 <factoryConfig>
  55.                         <!-- mysql ip -->
  56.                         <property name="ipAddress">10.10.10.50</property>
  57.                 </factoryConfig>
  58.         </dbServer>

  60.         <dbServer name="slave1" parent="abstractServer">
  61.                 <factoryConfig>
  62.                         <!-- mysql ip -->
  63.                         <property name="ipAddress">10.10.10.41</property>
  64.                 </factoryConfig>
  65.         </dbServer>

  67.         <dbServer name="slave2" parent="abstractServer">
  68.                 <factoryConfig>
  69.                         <!-- mysql ip -->
  70.                         <property name="ipAddress">10.10.10.42</property>
  71.                 </factoryConfig>
  72.         </dbServer>
  73. ####rp池配置的是salve1和slave2节点
  74.         <dbServer name="rp" virtual="true">
  75.                 <poolConfig class="com.meidusa.amoeba.server.MultipleServerPool">
  76.                         <!-- Load balancing strategy: 1=ROUNDROBIN , 2=WEIGHTBASED , 3=HA-->
  77.                         <property name="loadbalance">1</property>

  79.                         <!-- Separated by commas,such as: server1,server2,server1 -->
  80.                         <property name="poolNames">slave1,slave2</property>
  81.                 </poolConfig>
  82.         </dbServer>
  83. ####wp池配置的是master1和master2节点
  84.         <dbServer name="wp" virtual="true">
  85.                 <poolConfig class="com.meidusa.amoeba.server.MultipleServerPool">
  86.                         <!-- Load balancing strategy: 1=ROUNDROBIN , 2=WEIGHTBASED , 3=HA-->
  87.                         <property name="loadbalance">1</property>

  89.                         <!-- Separated by commas,such as: server1,server2,server1 -->
  90.                         <property name="poolNames">master1,master2</property>
  91.                 </poolConfig>
  92.         </dbServer>

  94. </amoeba:dbServers>
3、配置 amoeba.xml
  1. root@proxy:/usr/local/amoeba/conf# cat amoeba.xml
  2. <?xml version="1.0" encoding="gbk"?>

  4. <!DOCTYPE amoeba:configuration SYSTEM "amoeba.dtd">
  5. <amoeba:configuration xmlns:amoeba="http://amoeba.meidusa.com/">

  7.         <proxy>

  9.                 <!-- service class must implements com.meidusa.amoeba.service.Service -->
  10.                 <service name="Amoeba for Mysql" class="com.meidusa.amoeba.net.ServerableConnectionManager">
  11.                         <!-- port -->
  12.                         <property name="port">8066</property>

  14.                         <!-- bind ipAddress -->
  15.                         <!--
  16.                         <property name="ipAddress">127.0.0.1</property>
  17.                          -->

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

  21.                         <property name="connectionFactory">
  22.                                 <bean class="com.meidusa.amoeba.mysql.net.MysqlClientConnectionFactory">
  23.                                         <property name="sendBufferSize">128</property>
  24.                                         <property name="receiveBufferSize">64</property>
  25.                                 </bean>
  26.                         </property>

  28.                         <property name="authenticator">
  29.                                 <bean class="com.meidusa.amoeba.mysql.server.MysqlClientAuthenticator">

  31.                                         <property name="user">root</property>

  33.                                         <property name="password">root</property>

  35.                                         <property name="filter">
  36.                                                 <bean class="com.meidusa.amoeba.server.IPAccessController">
  37.                                                         <property name="ipFile">${amoeba.home}/conf/access_list.conf</property>
  38.                                                 </bean>
  39.                                         </property>
  40.                                 </bean>
  41.                         </property>

  43.                 </service>

  45.                 <!-- server class must implements com.meidusa.amoeba.service.Service -->
  46.                 <service name="Amoeba Monitor Server" class="com.meidusa.amoeba.monitor.MonitorServer">
  47.                         <!-- port -->
  48.                         <!-- default value: random number
  49.                         <property name="port">9066</property>
  50.                         -->
  51.                         <!-- bind ipAddress -->
  52.                         <property name="ipAddress">127.0.0.1</property>
  53.                         <property name="daemon">true</property>
  54.                         <property name="manager">${clientConnectioneManager}</property>
  55.                         <property name="connectionFactory">
  56.                                 <bean class="com.meidusa.amoeba.monitor.net.MonitorClientConnectionFactory"></bean>
  57.                         </property>

  59.                 </service>

  61.                 <runtime class="com.meidusa.amoeba.mysql.context.MysqlRuntimeContext">
  62.                         <!-- proxy server net IO Read thread size -->
  63.                         <property name="readThreadPoolSize">20</property>

  65.                         <!-- proxy server client process thread size -->
  66.                         <property name="clientSideThreadPoolSize">30</property>

  68.                         <!-- mysql server data packet process thread size -->
  69.                         <property name="serverSideThreadPoolSize">30</property>

  71.                         <!-- per connection cache prepared statement size -->
  72.                         <property name="statementCacheSize">500</property>

  74.                         <!-- query timeout( default: 60 second , TimeUnit:second) -->
  75.                         <property name="queryTimeout">60</property>
  76.                 </runtime>

  78.         </proxy>

  80.         <!--
  81.                 Each ConnectionManager will start as thread
  82.                 manager responsible for the Connection IO read , Death Detection
  83.         -->
  84.         <connectionManagerList>
  85.                 <connectionManager name="clientConnectioneManager" class="com.meidusa.amoeba.net.MultiConnectionManagerWrapper">
  86.                         <property name="subManagerClassName">com.meidusa.amoeba.net.ConnectionManager</property>
  87.                         <!--
  88.                           default value is avaliable Processors
  89.                         <property name="processors">5</property>
  90.                          -->
  91.                 </connectionManager>
  92.                 <connectionManager name="defaultManager" class="com.meidusa.amoeba.net.MultiConnectionManagerWrapper">
  93.                         <property name="subManagerClassName">com.meidusa.amoeba.net.AuthingableConnectionManager</property>

  95.                         <!--
  96.                           default value is avaliable Processors
  97.                         <property name="processors">5</property>
  98.                          -->
  99.                 </connectionManager>
  100.         </connectionManagerList>

  102.                 <!-- default using file loader -->
  103.         <dbServerLoader class="com.meidusa.amoeba.context.DBServerConfigFileLoader">
  104.                 <property name="configFile">${amoeba.home}/conf/dbServers.xml</property>
  105.         </dbServerLoader>

  107.         <queryRouter class="com.meidusa.amoeba.mysql.parser.MysqlQueryRouter">
  108.                 <property name="ruleLoader">
  109.                         <bean class="com.meidusa.amoeba.route.TableRuleFileLoader">
  110.                                 <property name="ruleFile">${amoeba.home}/conf/rule.xml</property>
  111.                                 <property name="functionFile">${amoeba.home}/conf/ruleFunctionMap.xml</property>
  112.                         </bean>
  113.                 </property>
  114. ####default池只配置了master1节点
  115.                 <property name="sqlFunctionFile">${amoeba.home}/conf/functionMap.xml</property>
  116.                 <property name="LRUMapSize">1500</property>
  117.                 <property name="defaultPool">master1</property>

  119.                 <property name="writePool">wp</property>
  120.                 <property name="readPool">rp</property>

  122.                 <property name="needParse">true</property>
  123.         </queryRouter>
  124. </amoeba:configuration>
4、启动amoeba
  1. root@proxy:/usr/local/amoeba# bin/amoeba start &
  2. [1] 2511
  3. root@proxy:/usr/local/amoeba#
  4. The stack size specified is too small, Specify at least 160k
  5. Could not create the Java virtual machine.

  7. [1]+ Exit 1 bin/amoeba start
更改bin/amoeba文件
  1. DEFAULT_OPTS="-server -Xms256m -Xmx256m -Xss128k"
  2. 更改为
  3. DEFAULT_OPTS="-server -Xms256m -Xmx256m -Xss256k"
启动正常之后，连接amoeba
  1. root@proxy:~# mysql -uroot -p -h10.10.10.39 -P8066
  2. Enter password:
  3. Welcome to the MySQL monitor. Commands end with ; or \g.
  4. Your MySQL connection id is 307988519
  5. Server version: 5.1.45-mysql-amoeba-proxy-2.2.0

  7. Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.

  9. Oracle is a registered trademark of Oracle Corporation and/or its
  10. affiliates. Other names may be trademarks of their respective
  11. owners.

  13. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

  15. java.util.NoSuchElementException: Could not create a validated object, cause: ValidateObject failed
  16. [root@10.10.10.39:(none)][11:46:57pm] MySQL-> at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1191)
  17.         at com.meidusa.amoeba.net.poolable.GenericObjectPool.borrowObject(GenericObjectPool.java:381)
  18.         at com.meidusa.amoeba.mysql.handler.CommandMessageHandler.startSession(CommandMessageHandler.java:633)
  19.         at com.meidusa.amoeba.mysql.handler.MySqlCommandDispatcher.handleMessage(MySqlCommandDispatcher.java:123)
  20.         at com.meidusa.amoeba.mysql.net.MysqlClientConnection$2.run(MysqlClientConnection.java:291)
  21.         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
  22.         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
  23.         at java.lang.Thread.run(Thread.java:662)
连接报错，查看root.log的输出
  1. 2015-08-29 16:01:03,299 INFO net.BackendConnectionFactory - open socket channel to server[10.10.10.40:3306]
  2. 2015-08-29 16:01:03,303 ERROR net.MysqlServerConnection - handShake with /10.10.10.40:3306 error:Access denied for user 'root'@'10.10.10.39' (using password: NO),hashCode=661272757
  3. 2015-08-29 16:01:03,324 INFO net.BackendConnectionFactory - open socket channel to server[10.10.10.50:3306]
  4. 2015-08-29 16:01:03,327 ERROR net.MysqlServerConnection - handShake with /10.10.10.50:3306 error:Access denied for user 'root'@'10.10.10.39' (using password: NO),hashCode=505588567
  5. 2015-08-29 16:01:03,331 INFO net.BackendConnectionFactory - open socket channel to server[10.10.10.41:3306]
  6. 2015-08-29 16:01:03,334 ERROR net.MysqlServerConnection - handShake with /10.10.10.41:3306 error:Access denied for user 'root'@'10.10.10.39' (using password: NO),hashCode=530654357
  7. 2015-08-29 16:01:03,335 INFO net.BackendConnectionFactory - open socket channel to server[10.10.10.42:3306]
  8. 2015-08-29 16:01:03,338 ERROR net.MysqlServerConnection - handShake with /10.10.10.42:3306 error:Access denied for user 'root'@'10.10.10.39' (using password: NO),hashCode=848649429
查看数据库连接权限
  1. [root@localhost:mysql][11:55:29pm] MySQL-> select host,user from user;
  2. +-----------+----------+
  3. | host | user |
  4. +-----------+----------+
  5. | % | rep_user |
  6. | % | root |
  7. | 127.0.0.1 | root |
  8. | ::1 | root |
  9. | localhost | |
  10. | localhost | root |
  11. | ubuntu | |
  12. | ubuntu | root |
  13. +-----------+----------+
  14. 8 rows in set (0.00 sec)
数据库权限正常，使用客户端连接测试
  1. root@proxy:~# mysql -uroot -p -h10.10.10.40
  2. Enter password:
  3. Welcome to the MySQL monitor. Commands end with ; or \g.
  4. Your MySQL connection id is 417
  5. Server version: 5.6.19-enterprise-commercial-advanced-log MySQL Enterprise Server - Advanced Edition (Commercial)

  7. Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.

  9. Oracle is a registered trademark of Oracle Corporation and/or its
  10. affiliates. Other names may be trademarks of their respective
  11. owners.

  13. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

  15. [root@10.10.10.40:(none)][11:59:09pm] MySQL-> use test;
  16. Reading table information for completion of table and column names
  17. You can turn off this feature to get a quicker startup with -A

  19. Database changed
  20. [root@10.10.10.40:test][11:59:12pm] MySQL-> show tables;
  21. +----------------+
  22. | Tables_in_test |
  23. +----------------+
  24. | t1 |
  25. +----------------+
  26. 1 row in set (0.00 sec)
客户端连接也正常，猜想应该是amoeba配置有问题
  1.                         <!-- mysql password
  2.                         <property name="password">111</property>
  3.                         -->
发现密码被注释了，更改
  1.                         <!-- mysql password -->
  2.                         <property name="password">111</property>
启动一切正常

  1. root@proxy:~# mysql -uroot -p -h10.10.10.39 -P8066
  2.     Enter password:
  3.     Welcome to the MySQL monitor. Commands end with ; or \g.
  4.     Your MySQL connection id is 1113757163
  5.     Server version: 5.1.45-mysql-amoeba-proxy-2.2.0 MySQL Enterprise Server - Advanced Edition (Commercial)

  7.     Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.

  9.     Oracle is a registered trademark of Oracle Corporation and/or its
  10.     affiliates. Other names may be trademarks of their respective
  11.     owners.

  13.     Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

  15.     [root@10.10.10.39:(none)][12:06:15am] MySQL-> use test;
  16.     Database changed
  17.     [root@10.10.10.39:test][12:06:18am] MySQL->
  18.     [root@10.10.10.39:test][12:06:18am] MySQL-> show tables;
  19.     +----------------+
  20.     | Tables_in_test |
  21.     +----------------+
  22.     | t1 |
  23.     +----------------+
  24.     1 row in set (0.00 sec)
5、测试读写分离
停止master2，slave1，slave2节点的复制
  1. [root@localhost:(none)][12:27:38am] MySQL-> stop slave;
  2. Query OK, 0 rows affected (0.04 sec)

  4. [root@localhost:(none)][12:27:53am] MySQL-> show slave status \G
  5. *************************** 1. row ***************************
  6.                Slave_IO_State:
  7.                   Master_Host: 10.10.10.40
  8.                   Master_User: rep_user
  9.                   Master_Port: 3306
  10.                 Connect_Retry: 60
  11.               Master_Log_File: master1-bin.000007
  12.           Read_Master_Log_Pos: 442
  13.                Relay_Log_File: slave-relay-bin.000008
  14.                 Relay_Log_Pos: 607
  15.         Relay_Master_Log_File: master1-bin.000007
  16.              Slave_IO_Running: No
  17.             Slave_SQL_Running: No
使用amoeba连接，往测试表t1中插入测试数据
  1. root@proxy:~# mysql -uroot -p -h10.10.10.39 -P8066
  2. Enter password:
  3. Welcome to the MySQL monitor. Commands end with ; or \g.
  4. Your MySQL connection id is 750410715
  5. Server version: 5.1.45-mysql-amoeba-proxy-2.2.0 MySQL Enterprise Server - Advanced Edition (Commercial)

  7. Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.

  9. Oracle is a registered trademark of Oracle Corporation and/or its
  10. affiliates. Other names may be trademarks of their respective
  11. owners.

  13. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

  15. [root@10.10.10.39:(none)][12:25:49am] MySQL-> use test;
  16. Database changed
  17. [root@10.10.10.39:test][12:26:51am] MySQL-> insert into t1 values (null,'aaaaa');
  18. Query OK, 1 row affected (0.05 sec)
master1查看表t1

  1. [root@localhost:mysql][11:27:16pm] MySQL-> select * from test.t1;
  2. +----+-------+
  3. | id | name |
  4. +----+-------+
  5. | 1 | aaaaa |
  6. +----+-------+
  7. 1 row in set (0.00 sec)
在master2，slave1，slave2上查看表t1

  1. [root@localhost:(none)][12:28:28am] MySQL-> use test;
  2. Reading table information for completion of table and column names
  3. You can turn off this feature to get a quicker startup with -A

  5. Database changed
  6. [root@localhost:test][12:29:17am] MySQL-> select * from t1;
  7. Empty set (0.00 sec)
在proxy上查看表t1表的数据

  1. [root@10.10.10.39:test][12:30:01am] MySQL-> select * from t1;
  2. Empty set (0.05 sec)
在proxy上无法查看插入的数据，说明读是在rp池里，而rp池只有slave1和slave2，数据没有同步到从节点。

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/12219480/viewspace-1786466/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/12219480/viewspace-1786466/

crj2951
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
odoo操作could not connect to server
qq_43239192的博客
01-04 1956
昨晚倒腾电脑，今天起床运行一下的项目看到这个。 出现这个错误：psycopg2.OperationalError: could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host “localhost” (::1) and accepting TCP/IP connec...
amoeba 使用笔记
u010066807的博客
03-18 758
环境延用mysql 主主+主从笔记的环境java version “1.8.0_73”安装wget http://nchc.dl.sourceforge.net/project/amoeba/Amoeba%20for%20mysql/2.2.x/amoeba-mysql-binary-2.2.0.tar.gzmkdir /opt/amoeba/ tar -zxvf amoeba-mysql-bin
Mysql基于Amoeba_读写分离搭架
01-17 9706
一、Amoeba简介 Amoeba是一个以MySQL为底层数据存储，并对应用提供MySQL协议接口的proxy。它集中地响应应用的请求，依据用户事先设置的规则，将SQL请求发送到特定的数据库上执行。基于此可以实现负载均衡、读写分离、高可用性等需求， Amoeba相当于一个SQL请求的路由器，目的是为负载均衡、读写分离、高可用性提供机制，而不是完全实现它们。需要结合使用MySQL的 Replic
amoeba实现mysql主从读写分离_使用Amoeba实现MySQL的主从读写分离
weixin_32541663的博客
01-19 285
前言：作者踏入Linux大门不久，这是第一个完成的功能演练。本文包含了MySQL+Amoeba实现主从读写分离的配置及个人过程中遇到的问题总结，网上相关教学也很多，如有错误和疏漏请多多指教。主从同步架构的优点读取工作交给了从服务器，降低了主服务器的压力在从服务器进行备份，避免备份期间影响主服务器服务当主服务器出现问题时，可以切换到从服务器。Amoeba介绍Amoeba(变形虫)项目,该开源框架于2...
读写分离Amoeba
weixin_30530939的博客
05-18 79
本想采用Mysql Proxy来实现读写分离，奈何其使用的lua脚本着实让人头痛，最后决定采用国人开发的开源数据库代理中间件Amoeba。使用Amoeba，只需要简单的xml配置，就可以很容易地实现读写分离。 Amoeba处于应用程序和数据库服务器之间，充当一个中间代理层。其支持负载均衡、高可用性、Query过滤、读写分离、可路由相关的query到目标数据库、可并发请求多台数据库合并结果。功能很...
Amoeba实现mysql读写分离
大道至简，持之以恒！
03-11 2543
一、关于读写分离 amoeba : 英[ə’mi:bə] 读写分离（Read/Write Splitting），基本的原理是让主数据库处理事务性增、改、删操作（INSERT、UPDATE、DELETE），而从数据库处理SELECT查询操作。 数据库复制被用来把事务性操作导致的变更同步到集群中的从数据库。 二、Amoeba 是什么 Amoeba(变形虫)项目，专注 分布式数据库 proxy 开发。座落与Client、DB Server(s)之间。对客户端透明。具有负载均衡、高可用性、sql过滤、读写分离、可路
Amoeba 实现MySQL读写分离
热门推荐
CSDN
05-12 1万+
Amoeba是一个以MySQL为底层数据存储,并对应用提供MySQL协议接口的proxy,它集中地响应应用的请求,依据用户事先设置的规则,将SQL请求发送到特定的数据库上执行.基于此可以实现负载均衡、读写分离、高可用性等需求,与MySQL官方的MySQL Proxy相比,作者强调的是amoeba配置的方便.
MySQL搭建Amoeba_读写分离.docx
12-25
MySQL 搭建 Amoeba 读写分离 在本文中，我们将详细介绍如何使用 Amoeba 实现 MySQL 读写分离的配置过程。Amoeba 是一个基于 MySQL 的 proxy，能够集中地响应应用的请求，并根据用户事先设置的规则，将 SQL 请求发送...
详解如何利用amoeba(变形虫)实现mysql数据库读写分离
12-16
在众多实现读写分离的方案中，Amoeba（变形虫）是阿里巴巴推出的一种基于Java的解决方案，它提供了更高效和稳定的性能。 Amoeba的工作原理是，它作为一个中间代理服务，接收来自应用的SQL请求，然后根据预设的策略...
windows平台用amoeba实现读写分离
06-12
具有负载均衡、高可用性、SQL 过滤、读写分离、可路由相关的到目标数据库、可并发请求多台数据库合并结果。 通过Amoeba能够完成多数据源的高可用、负载均衡、数据切片的功能，目前Amoeba已在很多企业的生产线上面...
amoeba 读写分离 配置说明
12-23
### Amoeba 读写分离配置详解 #### 一、配置前的准备工作 为了实现数据库的读写分离，首先需要确保所有的服务器均处于同一局域网内，并且完成以下准备工作： 1. **主机A（Amoeba服务器）**: - 安装 Java SE 1.6 ...
【MySQL 基于Amoeba读写分离】
很神秘的博客
07-29 644
在实际的生产环境中，如果对数据库的读和写都在同一个数据库服务器中操作，无论是安全性，高可用还是并发等各个方面都不能完全满足实际需求的，因此一般来说都是通过主从复制的方式来同步数据，再通过读写分离来提供数据的高并发负载能力这样的方案来进行部署。 简单来说，读写分离就是只在主服务器上写，只在从服务器上读，基本的原理是让主数据库处理事务性查询，而从数据库处理select查询，数据库复制被用来把事务性查询导致的改变更新同步到集群中的从数据库。
Amoeba高级配置
pty_2007的专栏
11-28 2044
做几个说明： 1.defaultPool是在writePool和readPool都为空的时候才会使用的；rule.xml里面配置的优先级比amoeba.xml里面配置的要高； 2.rule.xml里面的tableRule配置上用到的readPool和writePool，不要用默认值； 3.rule的表达式里面，case是可以嵌套case的。下面是我的一个比较复杂的写法：
Java基础（6）- Java代码笔记3
weixin_47062560的博客
08-30 1576
数据类型[][] 数组名 = new 数据类型[m][n]数据类型 数组名[][] = new 数据类型[m][n]数据类型[] 数组名[] = new 数据类型[m][n]m：代表二维数组长度n：代表二维数组中每个一维数组的长度。
浅析synchronized锁升级的原理与实现 1
最新发布
水w的博客
09-01 949
浅析synchronized锁升级的原理与实现
[C++规范] 访问类成员变量的方式：直接访问还是通过成员函数访问？
Loewen丶的小窝
08-26 1万+
在面向对象编程（OOP）中，通过成员函数（如`ME_HardwareTypeEnum Type() const;` 和 `int Id() const;`）来访问类的私有或受保护成员（如`m_hardwareType` 和 `m_id`），而不是直接通过公共成员访问，是一种更好的做法。
《深入理解 Java 中的适配器模式》
面团到油条的成长日记
08-29 7044
在软件开发的广阔领域中，不同接口之间不匹配的问题时常像个棘手的难题困扰着开发者。而适配器模式就像是一位得力的助手，专门用来解决这类问题。它的关键作用在于把一个类的接口有效地转化为客户端所期望的另一种接口，让原本因接口不相符而不能一起工作的两个类可以共同协作，学习本文希望你能有所收获
Java设计模式之建造者模式详细讲解和案例示范
weixin_39996520的博客
08-28 5485
建造者模式是一种创建型设计模式，允许用户通过一步步地构造复杂对象的方式来避免直接使用大量的构造函数或复杂的初始化过程。它通过将对象的创建过程分解为多个步骤，并允许这些步骤以链式调用的方式来执行，最终生成一个完全构建的对象。首先，我们定义一个Order类，该类包括了多个字段，如订单ID、客户信息、商品列表、配送地址等。// Getter方法省略...在这个例子中，类提供了构建Order对象所需的各个方法，每个方法返回实例，以便进行链式调用。
Amoeba指南：实现数据库集群与读写分离
Amoeba使用指南是一份详尽的文档，主要关注于如何在分布式环境中利用Amoeba实现数据库集群，特别针对MySQL和Oracle进行读写分离。Amoeba是一款分布式数据库代理，它能够管理和优化跨多个服务器的数据库操作，从而...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值