2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 6 mois
Contenus pertinents
- demandé il y a 7 mois
- Réponse acceptéedemandé il y a un an
- demandé il y a 4 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans