CODEWITHSUNDEEP
postgresqlamazon-rds
markvgti
markvgti

Reputation: 4619

Why does an RDS instance take > 2 hours to start?

New to AWS and RDS. Created a test db.t3.micro DB instance, used it for a few hours, then stopped it.

Today I started it, and over 2 hours later it's still showing "Starting...". Is this normal?

There is one database with one table with one row on that instance. The only thing I can see in the logs is: "Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered." (from roughly the time I gave the Start command via AWS console).

Update: the server finally started in 3 hrs 37 mins

Upvotes: 6

Views: 9099

Answers (1)

Exelian
Exelian

Reputation: 5888

Stopping and starting a DB will make AWS automatically create a snapshot (I was told during the AWS Sys admin course). Creating snapshots is very fast usually, but sometimes there are very large delays. My personal view is that this is probably some form of congestion on AWS' side, but I don't have an official comment to verify this.

Note that RDS instances aren't really ment to be shutdown and started up again. They're really ment to run continously. Starting/stopping instances has only been possible since 2017! https://aws.amazon.com/about-aws/whats-new/2017/06/amazon-rds-supports-stopping-and-starting-of-database-instances/.

My personal experience is that it's faster to create a snapshot and start a new instance from that, if possible in your use-case.

Edit: To clarify, 2 hours is NOT typical. In my experience a 500Gb DB will usually be restored in about 20-25 minutes. I'm afraid you're unlucky.

Upvotes: 3

Related Questions