Checking the Cluster Status¶
On the Clusters page of the GaussDB(DWS) management 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) management console. In the navigation tree on the left, click 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.
Enter the cluster name in the search box, and click to search for a cluster. Alternatively, in the All projects drop-down list above the cluster list, select the target project. Click to refresh the cluster list and billing mode. You can also click Search by Tag to search for clusters based on the criteria. 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.
Cluster name specified when a cluster is created.
After a cluster is created, its name cannot be changed.
Cluster running status. For details, see Cluster Status.
Cluster task status. For details, see Cluster Task Information.
Node flavors of clusters.
Enterprise project to which a cluster belongs.
Indicates that the cluster runs properly.
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, contact technical support engineers.
After the read-only status is canceled for the cluster, you are advised to perform the following operations:
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.
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.
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.
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.
A cluster goes into this state when it cannot provide database services. You are advised to contact technical support.
A cluster goes into this state when it is being created.
A cluster goes into this state when it fails to be created.
A cluster goes into this state when it is being restored from a snapshot.
Cluster Task Information¶
Indicates that a snapshot is being created in the cluster.
Snapshot creation failed
Indicates that a snapshot fails to be created.
Indicates that the system is storing modifications of cluster parameters.
Indicates that a cluster is being restarted.
Indicates that a cluster fails to be restarted.
Indicates that a cluster is being scaled out.
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.
Indicates that ELB is being associated.
Failed to associate ELB
Indicates that ELB fails to be associated.
Indicates that ELB is being disassociated.
Failed to disassociate ELB
Indicates that ELB fails to be disassociated.
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:
A cluster is being scaled in.
The cluster scale-in fails. You need to manually scale in the cluster again as soon as possible, or your services will be affected.
The primary/standby relationship of a cluster is being restored.
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.