Using Reader Instance in Aurora MYSQL

With the creation of a reading instance, a part of the load of SELECT queries goes to the reading instance. correct? But for example, let's assume that I put a reading instance of lesser capacity and this one is already with a high processing, when more readings arrive they will always go to that instance or the bank can take advantage of an idleness of the recording instance and forward some things for her?

주제

분석 데이터베이스

태그

아마존 Aurora 오로라 MySQL

언어

English

rePost-User-7704228

질문됨 일 년 전669회 조회

2개 답변

최신
최다 투표
가장 많은 댓글

수락된 답변

You need to specifically target the reader instance with your application. Any query routing would need to happen in the app as well.

Check out this doc page for more details: Replication with Amazon Aurora

C Mencarelli

답변함 일 년 전

Take a look at Amazon Aurora connection management.

You control where SELECTS are sent by connecting to an endpoint, Cluster, Reader, Instance, or Custom.

전문가

kentrad

답변함 일 년 전

rePost-User-7704228
일 년 전
Got it.but thinking about a scenario where my cluster only has one Reader. In case this Reader overloads with queries, is the load balanced with the Writer?
kentrad 전문가
일 년 전
You need to create a Custom (ANY) endpoint for that scenario.
kentrad 전문가
일 년 전
Also, take a look auto scaling your read replicas: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Integrating.AutoScaling.html

Using Reader Instance in Aurora MYSQL

관련 콘텐츠