AWS - Aurora 副本 [英] AWS - Aurora replicas

查看:45
本文介绍了AWS - Aurora 副本的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

场景:

  • 我有两个读取器-极光副本.
  • 我多次调用我的系统(高负载)
  • 我看到只有一个副本工作在 99.30%,但另一个没有什么都没有

为什么?,是因为第二个副本只是为了防止第一个的失败?不能让两者分担负载吗?

Why?, is because this second replica is ONLY to prevent failures of the first one?, cannot be possible to make both to share the load?

推荐答案

在 RDS 控制台中,您应该能够查看 3 个实例中的每一个

In your RDS console, you should be able to look at each of the 3 instances

  1. aurora-databasecluster-xxx.cluster-yyy.us-east-1.rds.amazonaws.com:3306
  2. zz0.yyy.us-east-1.rds.amazonaws.com:3306
  3. zz1.yyy.us-east-1.rds.amazonaws.com:3306

如果您查看集群选项卡,您将看到两个端点,第二个如下所示:aurora-databasecluster-xxx.cluster-ro-yyy.us-east-1.rds.amazonaws.com

If you look at the cluster tab you will see two end points and the 2nd is the following: aurora-databasecluster-xxx.cluster-ro-yyy.us-east-1.rds.amazonaws.com

Aurora 允许您明确访问特定的只读副本.这将允许一组只读节点用于 OLTP 性能,另一组用于数据分析 - 长时间运行的查询不会影响性能.

Aurora allows you do either explicitly get to specific read replica. This would allow a set of read only nodes for OLTP performance and another set for data analysis - with long running queries that won't impact performance.

如果您使用 -ro 端点,它应该平衡所有只读节点,或者您可以让您的代码获取只读连接字符串列表并执行您自己的随机化器.我本来希望 ro 会更好...但我还不熟悉他们的负载平衡技术(最少连接、循环等)

If you use the -ro end point, it should balance cross all read only nodes or you can have your code take a list of read only connection strings and do your own randomizer. I would have expected the ro to be better...but I am not yet familiar on their load balancing technique (fewest connections, round robin, etc)

这篇关于AWS - Aurora 副本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆