Help Center/
Relational Database Service/
FAQs/
Capacity Expansion and Specification Change/
Are My RDS DB Instances Still Available During Storage Scale-up and Instance Class Change?
Updated on 2024-05-31 GMT+08:00
Are My RDS DB Instances Still Available During Storage Scale-up and Instance Class Change?
Currently, you can scale up storage space and change the vCPU or memory of a DB instance.
- When storage space is being scaled up, RDS DB instances are still available and services are not affected. However, you cannot delete or reboot DB instances that are being scaled.
- After you change the instance class of a DB instance, the DB instance will be rebooted and the cache in the memory will be automatically cleared. To prevent service interruption, perform the operation during off-peak hours. Changing an instance class during peak hours will take much more time.
When you change the instance class of a primary/standby instance, service downtime only occurs during the primary/standby switchover. The duration of the downtime varies from seconds to minutes based on the replication delay and the number of temporary files. Perform the operation during off-peak hours.
References
- Scaling Up Storage Space of an RDS for MySQL Instance
- Changing a DB Instance Class for RDS for MySQL
- Scaling Up Storage Space of an RDS for MariaDB Instance
- Changing a DB Instance Class for RDS for MariaDB
- Scaling Up Storage Space of an RDS for PostgreSQL Instance
- Changing a DB Instance Class for RDS for PostgreSQL
- Scaling Up Storage Space of an RDS for SQL Server Instance
- Changing a DB Instance Class for RDS for SQL Server
Parent topic: Capacity Expansion and Specification Change
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
