DB Instance Status

DB Instance Status

Table 1 Status and description

Status

Description

Available

A DB instance is running properly.

Abnormal

A DB instance is faulty.

Unhealthy

A node in an available cluster or replica set instance is abnormal or unknown.

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

The Show Original Log function is enabled.

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. Frozen instances are unfrozen only after your account is recharged and the overdue payments are cleared.

Parameter Template Status

Table 2 Status and description

Status

Description

In-Sync

A database parameter change has taken effect.

Pending restart

A database parameter is waiting for the DB instance to be restarted for the modification to take effect.