1 Answer
- Newest
- Most votes
- Most comments
0
There are a few things you can check based on the information provided:
- Verify the maintenance window for the RDS instance and check if any maintenance was scheduled during this time. Forced maintenance could cause performance impacts.
- Check the CloudWatch metrics for the database, particularly CPU utilization, to see if the instance is overprovisioned after the maintenance. Rebooting the instance may help if resources are not released.
- For SQL Server, review the SQL Server error log for any errors or warnings reported around the maintenance period.
- If using a single-AZ deployment, the storage volumes may need to be restored from backup after forced maintenance, causing temporary performance penalties until volumes are restored.
- For read replicas, check the replication lag metric to ensure the replica has caught up fully. Excessive lag can cause latency.
- Consider changing the instance type temporarily to a larger size to handle increased load until performance stabilizes again
- As a last resort, you can restore the database from the latest backup to fully refresh the data and storage.
Relevant content
- asked a year ago
- asked 10 months ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 6 months ago