- 最新
- 投票最多
- 评论最多
We're absolutely having the same problem over here: https://repost.aws/questions/QUIK9smsSVTriFJ3ynQ8w7iw#AN9SjEmXfuSmeQpjJhnhPF_w
We're reluctant to pay for AWS Support for something that seems like it's on AWS's end.
Additionally, we're now seeing the same thing on another database in the same AZ which is disconnected from the application. Started at just before midnight US/Eastern. Spiked to 3000 IOPS and almost drained all of our burst credits.
From what you described above, it may be an issue with underlying EBS volumes. Please have AWS support check in for you and raise support case if you have not already done so and we should be able to help by looking at your instance.
Should I get the developer support plan ?
GP2 with 170GB has a burst performance upto 3000 IOPS, and base performance of 170x3 = 510 IOPS. You can find detail here:
yes I know that, the problem isn't the base performance/burst capacity, its the spike that can go up to 3000 IOPS for a minute, every 15 minute, that start suddenly just 3 days ago
相关内容
- 已提问 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 8 个月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
fikrimi, we seem to be seeing relief on our end. Wondered if you were seeing the same?
looks good as of 31 Jan