- Newest
- Most votes
- Most comments
Unfortunately there was a defective underlying storage volume on one of your disk. The defect was detected automatically and the volume was replaced. Your performance should be back to normal.
You should be able to look at the Enhanced Monitoring physical io metrics from this period and see that one of your volumes had elevated latencies for a period
Sorry for the inconvenience.
-Phil
As far as I know, the defect was not detected automatically, but required creating a case with AWS support to correct. I'm noting this so that if anyone else runs into the same issue, they won't wait too long expecting it to resolve on its own. We experienced approximately 8 hours of degraded service because of this problem.
It's also worth noting that because RDS performs a synchronous write to both the primary and standby EBS volumes, elevated latency in either AZ can cause this problem. Manual failover will not help because the same two volumes are still being written to by the new primary instance.
Relevant content
- asked a year ago
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago