nav-img
Advanced

Checking the GaussDB(DWS) Cluster Status

Choose Dedicated Clusters > Clusters and you can view the general information about a cluster in the displayed cluster list, such as the cluster status, task information, recent events, and node specifications.

Querying General Information of a Cluster

Log in to the GaussDB(DWS) console. In the navigation pane, choose Dedicated Clusters > 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, cluster version, 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.

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.

Cluster Version

Version of the current cluster. For details, see Table 3.

Task Information

Cluster task status. For details, see Cluster Task Information.

Node Flavor

Node flavors of clusters.

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

Cluster Status

VACUUM FULL;

Cluster Version

Table 3 Cluster version

Version

Description

x.x.x

Current cluster version. To improve system stability, click Upgradable to go to the upgrade management page. For details, see Upgrading a GaussDB(DWS) Cluster.

Cluster Task Information

Table 4 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.

  • 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

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.