Hello there, We have enabled Auto Scaling for one of our RDS Aurora MySQL Cluster. Writer Size: db.r6g.2xlarge Reader Size: db.r6g.large - Whenever scale out happens, it creates new instance with the same size as Writer node(in this case size is db.r6g.2xlarge). We expected it to create new instances with same size as Reader node(db.r6g.large). - Also the new instance doesn't inherit the tags from the cluster. If it's not bug, please take this as feature request

RDS Auto Scaling - Bug/feature request

Hello there,

We have enabled Auto Scaling for one of our RDS Aurora MySQL Cluster.

Writer Size: db.r6g.2xlarge

Reader Size: db.r6g.large

Whenever scale out happens, it creates new instance with the same size as Writer node(in this case size is db.r6g.2xlarge). We expected it to create new instances with same size as Reader node(db.r6g.large).
Also the new instance doesn't inherit the tags from the cluster.

If it's not bug, please take this as feature request

Higher
1年前
As best practice you should have the WRITER and the READER with the same size, in case of failover your reader could get short on resources if they are different.

トピック

移行と近代化分析データベース管理とガバナンス

タグ

Amazon Relational Database Service (RDS)AWS Auto Scaling Aurora MySQL

言語

English

AWS-User-0417258

質問済み 1年前277ビュー

1回答

新しい順
投票が多い順
コメントが多い順

承認された回答

Hello,

As per this documentation, When Aurora Auto Scaling adds a new Aurora Replica, the new Aurora Replica is the same DB instance class as the one used by the primary instance. This is recommended as in case the reader promoted as writer, to give similar performance as old writer.

However, understand your requirements to have configurable instance types while autoscaling aurora replicas. Will forward this feature request . Thank you !

Thank you !

gokul_guna

回答済み 1年前

RDS Auto Scaling - Bug/feature request

関連するコンテンツ