RDS Auto Scaling - Bug/feature request

0

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

  • 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.

1 個回答
2
已接受的答案

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 !

AWS
已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南