Checking the 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, recent events, and enterprise project). Click 
to refresh the cluster list. 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.
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. |
Enterprise Project | Enterprise project to which a cluster belongs. |
Operation |
|
Cluster Status¶
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:
|
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. |
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¶
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. |
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. |
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.
|
Changing node flavor | The cluster is being scaled. |
Node flavor change failed | All specifications change failed |
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. |