2 個答案
- 最新
- 最多得票
- 最多評論
0
I think the issue here is that you are running out of available IOPS capacity on the ec2 instance class you've selected. Eg, this instance has a max iops of 20k.
$ aws ec2 describe-instance-types --instance-types m6g.4xlarge --query "InstanceTypes[*].[InstanceType, EbsInfo.EbsOptimizedSupport, EbsInfo.EbsOptimizedInfo]"
[
[
"m6g.4xlarge",
{
"BaselineBandwidthInMbps": 4750,
"BaselineThroughputInMBps": 593.75,
"BaselineIops": 20000,
"MaximumBandwidthInMbps": 4750,
"MaximumThroughputInMBps": 593.75,
"MaximumIops": 20000
}
]
]
0
After I changed the disk configuration, iops from 12000 to 13000, I did this modification to triggle the storage optimization action. And the disk io await goes to normal state. Very strange.
已回答 6 個月前
相關內容
- 已提問 10 個月前
- 已提問 6 個月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前