- 新しい順
- 投票が多い順
- コメントが多い順
By default, Aurora Serverless v2 needs scaling point to scaling up and down to meet required capacity. The Force the capacity change option isn't selected by default. Keep this option clear to have your Aurora Serverless v1 DB cluster's capacity remain unchanged if the scaling operation times out without finding a scaling point. Selecting this option causes your Aurora Serverless v1 DB cluster to enforce the capacity change, even without a scaling point.
Lost connection to MySQL server at 'reading initial communication packet
this error might be caused due to the lack of capacity on Aurora Serverless side. Please consider enabling Force the capacity change
option. But please be careful, and recommend review the below document before tern this setting ON.
Please see more detail on our document: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v1.how-it-works.html#aurora-serverless.how-it-works.timeout-action
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 3年前
- AWS公式更新しました 1年前