- Newest
- Most votes
- Most comments
Database recovery is performed on every startup even after a clean shutdown. This is quite normal and not at all an issue.
Database recovery is a normal way to make sure that the database log files are correctly applied or rolled back to maintain transactional correctness.
My guess is that when you stop an RDS instance it doesn't wait for all transactions to finish (as this could cause a delay in the stopping of the database.). Instead it immediately kills all connections and stops the database. This may leave the database in a state where there are committed items in the logs that still need to be applied or uncommitted items in the logs that need to be rolled back in order to get the database into a proper transactional running state.
Thank you for your answer @joelrwilliams1! So, your thought , like mine, is that the database is not on a "stable" state, that something went wrong when the RDS instance was stopped. Well, I'm agree, but I'm trying to find out what / who is the cause... And I can assure it's not my fault, because I take care to have not open connections to the instance when I stop the database, it happens every time with every instance, even with new created instances: I create it, I don't tell anyone the host name, user or password, even the security group doesn't allow anyone to access to the mariadb instance, so no user connections exist, I wait for the instance to be in Avalaible state ... and then in actions I click on "Stop temporarily" ... and yet, when I restart the Instance the "Recovery of the DB instance has started" happens, so I'm afraid that using this feature are endangering my database and my data. Could anyone else try to reproduce this behaviour? As my point of view, is AWS who are not stopping database in an orderly and gentle way ... Could anyone from AWS shed any light on this matter? Thanks again and best regards
Relevant content
- asked a year ago
- asked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- How do I resolve the storage full issue on my RDS for MySQL instance or my RDS for MariaDB instance?AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
It's a relief that someone at AWS states that is quiet normal and not an issue! Anyway, it would be great that it was stated in the documentation as well. And why these events are registered twice?