What's New
Function Overview
Product Bulletin
- Product Notice
- Version Support Notes
Service Overview
- GaussDB(DWS) Infographics
- What Is GaussDB(DWS)?
- Data Warehouse Types
- Data Warehouse Flavors
- Advantages
- Application Scenarios
- Functions
- Concepts
- Related Services
- Security
- GaussDB(DWS) Permissions Management
- GaussDB(DWS) Access
- Restrictions
- Technical Support
- Service Quotas
- GaussDB(DWS) Technical Specifications
Billing
- GaussDB(DWS) Billing Overview
- Billing Modes
- Item
- Billing Examples
- Billing Mode Change
- Renewal
  - Overview
  - Manual Renewal
- Bills
- Arrears
- Stopping Billing
- Cost Management
- Billing FAQs
Getting Started
- Checkpoint Vehicle Analysis
- Supply Chain Requirement Analysis of a Company
- Operations Status Analysis of a Retail Department Store
- Creating a Time Series Table
- Best Practices of Hot and Cold Data Management
- Best Practices for Automatic Partition Management
- Creating a Cluster and Connecting to It
- Using CDM to Migrate MySQL Data to the GaussDB(DWS) Cluster
- Using DLI Flink Jobs to Write Kafka Data to GaussDB(DWS) in Real Time
- Basic SQL Operations
- Database Quick Start
- Getting Started with Common Practices
User Guide
- Using GaussDB(DWS)
- Preparations
- Creating a GaussDB(DWS) Cluster
- Connecting to a GaussDB(DWS) Cluster
- Creating a GaussDB(DWS) Database and User
- Migrating Service Data to a GaussDB(DWS) Cluster
  - Migrating Data to a GaussDB(DWS) Cluster Using GDS-Kafka
  - Data Source Management
- GaussDB(DWS) Cluster Data Security and Encryption
- GaussDB(DWS) Cluster Management
- GaussDB(DWS) Cluster O&M
Best Practices
- Import and Export
- Data Migration
- Data Analytics
- Decoupled Storage and Compute
  - DWS 3.0 Decoupled Storage and Compute Usage Suggestions and Performance Optimization
- Data Development
- Database Management
- Performance Tuning
  - Optimizing Table Structure Design to Enhance GaussDB(DWS) Query Performance
  - Analyzing SQL Statements That Are Being Executed to Handle GaussDB(DWS) Performance Issues
- Cluster Management
  - Binding Different Resource Pools to Two Types of Jobs to Balance Load for GaussDB(DWS)
  - Scaling Options for GaussDB(DWS) with a Coupled Storage-Compute Architecture
Data Migration and Synchronization
- Data Migration to GaussDB(DWS)
- Importing Data
- Full Database Migration
  - Using CDM to Migrate Data to GaussDB(DWS)
  - Using DSC to Migrate SQL Scripts
- Real-time Import
  - Using DRS to Import Data to GaussDB(DWS)
  - Real-time Data Import From Kafka GaussDB(DWS)
- Metadata Migration
  - Using gs_dump and gs_dumpall to Export Metadata
  - Using gs_restore to Import Data
- Exporting Data
- Other Operations
Developer Guide
- Standard Data Warehouse (9.1.0.x)
- Standard data warehouse (8.1.3.x)
- Hybrid Data Warehouse (9.1.0.x）
- Hybrid Data Warehouse (8.1.3.x）
- Historical Versions
SQL Syntax Reference
- SQL Syntax Reference (9.1.0.x)
- SQL Syntax Reference (8.1.3.x)
- Historical Versions
Performance Tuning
- Overview of Query Performance Optimization
- Query Execution Process
- SQL Execution Plan
- SQL Optimization Guide
- Optimization Cases
- SQL Execution Troubleshooting
- query_band Load Identification
- Common Performance Parameter Optimization Design
Tool Guide
- Overview
- Downloading Related Tools
- gsql
- Data Studio
- GDS
- DSC
- DataCheck
- DWS-Connector
- Server Tool
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- API Description
- Application Cases
  - Using Postman to Call the API for Creating a Cluster
  - Using Postman to Call the API for Creating a Snapshot
- Introduction
- Appendix
SDK Reference
- SDK Overview
FAQs
- Top FAQs
- Product Consulting
- Database Connections
- Data Migration
- Database Usage
- Cluster Management
- Account Permissions
- Database Performance
- Backup and Restoration
  1. Why Does It Take a Long Time to Create an Automated Snapshot in GaussDB(DWS)?
  2. Does a GaussDB(DWS) Snapshot Have the Same Function as an EVS Snapshot?
Troubleshooting
- Database Connections
- JDBC/ODBC
- Data Import and Export
- Database Parameter Modification
- Account/Permission/Password
- Cluster Performance
- Cluster Exceptions
  - The Disk Usage Alarm Is Frequently Generated
- Database Use
Videos
Performance White Paper
- Overview
- Test Result
  - TPC-H Single Query Test
  - TPC-DS Single Query Test
- Test Methods
- Appendixes
  - TPC-H Test Sets
  - TPC-DS Test Sets
Technical White Paper
- GaussDB(DWS)
- Platforms and Technical Specifications Supported by GaussDB(DWS)
  - Technical Specifications
- GaussDB(DWS) Core Technologies
- GaussDB(DWS) Tools
  - Client Tools
  - Database Monitoring Tool
- External APIs
Error Code Reference
- 8.2.0 and earlier versions
  - Management Console Error Code
  - Data Warehouse Service Error Codes
- 8.2.1 or later versions
Glossary
More Documents
- User Guide
- API Reference (ME-Abu Dhabi Region)
- Developer Guide (ME-Abu Dhabi Region)
- SQL Syntax Reference (ME-Abu Dhabi Region)
- Tool Guide (ME-Abu Dhabi Region)
- Error Code Reference (ME-Abu Dhabi Region)
  - Management Console Error Code
- User Guide (Paris Region)
- API Reference (Paris Region)
- Developer Guide (Paris Region)
- SQL Syntax Reference (Paris Region)
- Tool Guide (Paris Region)
- Error Code Reference (Paris Region)
  - Management Console Error Code
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
- Developer Guide (Kuala Lumpur Region)
- SQL Syntax Reference (Kuala Lumpur Region)
- Tool Guide (Kuala Lumpur Region)
- Error Code Reference (Kuala Lumpur Region)
  - Management Console Error Code
General Reference
- Glossary
- Service Level Agreement
- White Papers
- Endpoints
- Permissions

On this page

Show all

Help Center/ GaussDB(DWS)/ User Guide/ GaussDB(DWS) Cluster Management/ Checking the GaussDB(DWS) Cluster Status

Checking the GaussDB(DWS) Cluster Status

Updated on 2025-03-03 GMT+08:00

View PDF

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, 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.
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. 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 GaussDB(DWS) Cluster. Monitoring Panel: For details, see Viewing GaussDB(DWS) Cluster Monitoring Information on the Monitoring Panel (DMS). More Convert to Encryption Cluster: For details, see Converting an Ordinary Cluster to an Encrypted Cluster. View Metric: For details, see Viewing GaussDB(DWS) Cluster Monitoring Information on Cloud Eye. Restart: Click Restart to restart a cluster. For details, see Restarting a cluster. Start: Click Start to start a stopped cluster. For details, see Starting a Cluster. Stop: Click Stop to stop a running cluster. For details, see Stopping a Cluster. Scale Node: For details, see Scaling GaussDB(DWS) Cluster Nodes. Change Specifications: For details, see Changing GaussDB(DWS) Cluster Specifications. Reset Password: For details, see Resetting the Password the GaussDB(DWS) Database Administrator. Create Snapshot: For details, see Backing Up and Restoring a GaussDB(DWS) Cluster. Delete: Click Delete to delete a cluster. 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, 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 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. 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 5** 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.