Instance Statuses
The status of an instance reflects the health of the instance. You can use the management console or API to view the status of a DB instance.
DB Instance Status
Status |
Description |
---|---|
Available |
A DB instance is running properly. |
Abnormal |
A DB instance is faulty. |
Creating |
A DB instance is being created. |
Creation failed |
A DB instance fails to be created. |
Backing up |
An instance backup is being created. |
Restarting |
A DB instance is being restarted because of a modification that requires restarting it for the modification to take effect. |
Switchover in progress |
The primary and standby nodes of the replica set instance or the primary and standby shards or configs of a cluster instance are being switched over. |
Adding node |
shard or mongos nodes are being added to a DDS cluster instance. |
Deleting node |
The node that failed to be added is being deleted. |
Scaling up |
The storage space of instance nodes is being expanded. |
Changing instance class |
The CPU or memory of a DB instance is being changed. |
Changing to yearly/monthly |
The billing mode is being changed from pay-per-use to yearly/monthly. |
Checking restoration |
The backup of the current DB instance is being restored to a new DB instance. |
Restoring |
The backup is being restored to the existing DB instance. |
Restore failed |
Restoring to the existing DB instance failed. |
Switching SSL |
The SSL channel is being enabled or disabled. |
Querying original slow query logs |
Show Original Log is being enabled or disabled. |
Changing private IP address |
The private IP address of a node is being changed. |
Changing port |
The DB instance port is being changed. |
Changing a security group |
The security group is being changed. |
Frozen |
DB instances are frozen when there is no balance in the account. |
Minor version upgrade |
The minor version upgrade is in progress. |
Checking changes |
Status of a yearly/monthly instance when the billing mode is being changed. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.