Checking the GaussDB(DWS) Cluster Status

On the Clusters > Dedicated Clusters page of the GaussDB(DWS) console, you can view the general information about a cluster in the cluster list, such as the cluster status, task information, recent events, and node flavor.

Querying General Information of a Cluster

Log in to the GaussDB(DWS) console. In the navigation pane, click Clusters > Dedicated Clusters. The cluster list displays all clusters. If there are a large number of clusters, you can turn pages to view the clusters in any status.

In the upper part of the cluster list, click the search box and search for the required cluster based on the filter criteria (cluster name, cluster status, task information, node specifications, billing mode, recent events, and enterprise project). Click to refresh the cluster list and billing mode. You can also click Search by Tag to search for clusters based on cluster tags. For details, see Searching for Clusters Based on Tags.

Clusters are listed in chronological order by default, with the most recent clusters displayed at the top. Table 1 describes the cluster list parameters.

**Table 1** Cluster list parameters
Parameter	Description
Cluster Name	Cluster name specified when a cluster is created. NOTE: If the cluster name cannot be changed on the console, contact technical support.
Cluster Status	Cluster running status. For details, see Cluster Status.
Task Information	Cluster task status. For details, see Cluster Task Information.
Node Flavor	Node flavors of clusters. For details, see GaussDB(DWS) Pricing.
Billing Mode	Cluster billing mode. In pay-per-use mode, the cluster creation time is displayed. In yearly/monthly mode, the cluster expiration time is displayed. For details, see Yearly/Monthly.
Recent Events	Number of recent events in a cluster. You can click the number to view event details.
Enterprise Project	Enterprise project to which a cluster belongs.
Operation	Log In: For details, see Using the SQL Editor to Connect to a Cluster. Monitoring Panel: For details, see Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS). More View Metric: For details, see Viewing GaussDB(DWS) Cluster Monitoring Information on Cloud Eye. Restart: Click Restart to restart a cluster. For details, see Starting, Stopping, and Deleting a GaussDB(DWS) Cluster. Scale Out: For details, see Scaling Out a Cluster. Change all specifications: For details, see Changing All Specifications. Scale In: For details, see Scaling In a Cluster. Redistribute: For details, see Redistributing Data. Expand Disk Capacity: For details, see Disk Capacity Expansion of an EVS Cluster. Reset Password: For details, see Resetting the Password the GaussDB(DWS) Database Administrator. Create Snapshot: For details, see Manual Snapshots. Delete: Click Delete to delete a cluster. For details, see Deleting a Cluster. Change node flavor: For details, see Changing the Node Flavor. Manage CN: For details, see Adding or Deleting a CN in a GaussDB(DWS) Cluster.

Cluster Status

Table 2 Cluster status description

Status

Description

Available

Indicates that the cluster runs properly.

Read-only

A cluster goes into this state when the disk usage of the cluster or a single node in the cluster is greater than 90%. The cluster can still work in this state but supports only query operations. Write operations are not supported. When the cluster status becomes read-only, remove the status by referring to Removing the Read-only Status. If the status cannot be removed, contact technical support engineers.

After the read-only status is canceled for the cluster, you are advised to perform the following operations:

Use the SQL client tool to connect to the database as the administrator and run the following command to periodically clear and reclaim the storage space:

           
                VACUUM FULL;

After you delete data stored in GaussDB(DWS) data warehouses, dirty data may be generated possibly because the disk space is not released. This results in disk space waste. It is recommended that the storage space be cleared periodically.

You are advised to check the disk capacity and analyze whether the existing cluster specifications meet service requirements. If not, expand the cluster capacity. For details, see Scaling Out a Cluster.

Unbalanced

If the role of a GTM or DN in the cluster is different from the initial role, the cluster is in the Unbalanced state. In the Unbalanced state, the number of primary instances on some nodes increases. As a result, the load pressure is high. In this case, the cluster is normal, but the overall performance is not as good as that in a balanced state. You are advised to switch a cluster to the Available state during off-peak hours. For details, see Performing a Primary/Standby Switchback.

Redistributing

A cluster goes into this state when it detects that the service data on the original nodes is significantly larger than that on the new node after a new node is added to the cluster. In this case, the system automatically redistributes data on all nodes. The cluster can still work in this state.

Redistribution failed

A cluster goes into this state when data redistribution fails, but no data loss occurs. The cluster can still work in this state. You are advised to contact technical support.

Degraded

A cluster goes into this state when some nodes in the cluster are faulty, but the whole cluster runs properly. You are advised to contact technical support.

Unavailable

A cluster goes into this state when it cannot provide database services. You are advised to contact technical support.

Creating

A cluster goes into this state when it is being created.

Creation failed

A cluster goes into this state when it fails to be created.

Creating, restoring

A cluster goes into this state when it is being restored from a snapshot.

Deleting

A cluster goes into this state when it is being deleted.

Frozen for legal reasons

Indicates that the cluster is frozen for legal reasons. In this case, the cluster cannot be deleted or unsubscribed, and its name cannot be changed.

Frozen

Indicates that the cluster is frozen (excluding legal reasons). In this case, the cluster name cannot be changed.

If your account balance is insufficient and fee deduction fails, the retention period starts. During the retention period, the service resources will be frozen and cannot be used, but resources and data are reserved. To unfreeze the clusters, you need to top up your account to ensure that the account balance is not 0. For details, see How Do I Renew My Service?

To be restarted

This status indicates that GUC parameters have been modified in the cluster and the modification can take effect only after the cluster is restarted. Before the cluster is restarted, some O&M operations cannot be performed. After you manually restart the cluster, the GUC parameter takes effect and the cluster status changes to Available.

Stopped

Indicates that the cluster is stopped.

Cluster Task Information

**Table 3** Task information description
Status	Description
Creating snapshot	Indicates that a snapshot is being created in the cluster.
Snapshot creation failed	Indicates that a snapshot fails to be created.
Observing	Indicates that the cluster is to be submitted after the automatic upgrade.
Configuring	Indicates that the system is storing modifications of cluster parameters.
Restarting	Indicates that a cluster is being restarted.
Restart failed	Indicates that a cluster fails to be restarted.
Converting to encryption cluster	Indicates that the cluster is being converted to an encrypted cluster.
Encryption cluster conversion failed	Indicates that the cluster fails to be encrypted.
Scaling out	Indicates that a cluster is being scaled out.
Scale-out failed	Indicates that a cluster fails to be scaled out.
Expanding disk capacity	Indicates that disk capacity is being expanded.
Disk expansion failed	Indicates that disk capacity fails to be expanded.
Associating ELB	Indicates that ELB is being associated.
Failed to associate ELB	Indicates that ELB fails to be associated.
Disassociating ELB	Indicates that ELB is being disassociated.
Failed to disassociate ELB	Indicates that ELB fails to be disassociated.
Checking scale-in	The service is checking whether a cluster can be scaled in.
Scale-in check failed	A cluster does not meet the scale-in requirements. For example: The value of default_storage_nodegroup is not installation. In the cluster database, data_redis is a reserved redistribution schema, but the schema contains user tables. The cluster disk space does not meet the scale-in requirements. For details, see Scaling In a Cluster.
Scaling in	A cluster is being scaled in.
Scale-in failed	The cluster scale-in fails. You need to manually scale in the cluster again as soon as possible, or your services will be affected.
Switching back	The primary/standby relationship of a cluster is being restored.
Switchback failed	The primary/standby relationship of a cluster fails to be restored. Possible causes are as follows. For details, see Management Plane Error Code Reference. Redo operations are being performed on DNs. Wait until the operations are completed and try again. Failed to query DN redo information. Check tenant logs to identify the failure cause. Primary/standby catchup is in progress. Wait until it is completed and try again. Failed to query primary/standby catchup information. Check tenant logs to identify the failure cause. Primary/standby catchup failed. Contact technical support or try again later. Check tenant logs to identify the failure cause. The cluster is abnormal.
Changing node flavor	The cluster is being scaled.
Node flavor change failed	All specifications change failed
Waiting for payment	The order for changing a pay-per-use cluster to a yearly/monthly cluster has not been paid. After the order is paid or canceled, the status will change.
Changing all specifications	All the specifications of the cluster being changed.
All specifications change failed	Specifications change failed because of insufficient quotas or permissions, or abnormal cluster status.
Maintaining	A maintenance change operation, such as cluster upgrade or plug-in upgrade, is being performed on the cluster.
Maintain_failure	A cluster fails to be restarted.
Stopping	Indicates that the cluster is being stopped.
Starting	Indicates that the cluster is being started.
Inspecting	Indicates that the cluster is being inspected before the change.
Inspection failed	Indicates that the cluster inspection fails.

Yearly/Monthly

**Table 4** Yearly/Monthly billing mode description
Status	Description
Expire in XX	Remaining duration of a yearly/monthly cluster. You can renew the subscription, change the payment mode to pay-per-use, and unsubscribe from the subscription.
Expired. XX until frozen	A yearly/monthly cluster enters the grace period if it is not renewed upon expiration. In the grace period, a yearly/monthly cluster is still available and can be renewed, but it cannot be changed to pay-per-use or unsubscribed from.
Frozen. XX until deletion	The grace period of a yearly/monthly cluster ends and the cluster enters the retention period. The cluster can be renewed, but it cannot be changed to pay-per-use or unsubscribed from.
Change to pay-per-use after XX	After the validity period of a yearly/monthly cluster expires, the cluster becomes a pay-per-use cluster. The cluster can be renewed or unsubscribed from, but it cannot be changed to pay-per-use.
Frozen (due to violation)	Frozen by public security institutions. The cluster can be renewed, but it cannot be changed to pay-per-use or unsubscribed from. The cluster still incurs charges during the freezing period.
Frozen (due to violation) and will be deleted after XX	Frozen due to violations of regulations. The cluster can be renewed, but it cannot be changed to pay-per-use or unsubscribed from. The cluster still incurs charges during the freezing period.