yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
3a18074b3713bb016a8cceda6cd6cc62781dcff1
doc-exports/docs/dws/umn/dws_01_0035.html
luhuayi 3a18074b37 DWS UMN 20250703 version 
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: luhuayi <luhuayi@huawei.com>
Co-committed-by: luhuayi <luhuayi@huawei.com>
2025-08-04 06:51:42 +00:00

7.1 KiB
Raw Blame History

Handling Abnormal GaussDB(DWS) Clusters

Removing the Read-only Status

A cluster in read-only status does not allow write operations. You can remove this status on the management console. A cluster becomes read-only probably because of high disk usage. For how to solve this problem, see "Solution to High Disk Usage and Cluster Read-Only" in Data Warehouse Service (DWS) Troubleshooting Guide.

  • Clusters of version 1.7.2 or later support removal of the read-only state.
  • In 8.2.0 and later versions, you can free up disk space by using DROP/TRUNCATE TABLE in a read-only cluster.

Impacts on the System

  • You can cancel the read-only status only when a cluster is read-only.
  • When a cluster is in read-only status, stop the write tasks to prevent data loss caused by used up disk space.
  • After the read-only status is canceled, clear the data as soon as possible to prevent the cluster from entering the read-only status again after a period of time.

Procedure

  1. Log in to the GaussDB(DWS) console.
  2. Choose Dedicated Clusters > Clusters.

    All clusters are displayed by default.

  3. In the row containing the cluster whose cluster status is Read-only, click Cancel Read-only.
  4. In the dialog box that is displayed, click OK to confirm and remove the read-only status for the cluster.

Performing a Primary/Standby Switchback

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. Restore the primary-standby relationship to recover the cluster to the available state.

  • Only 8.1.1.202 and later versions support primary/standby cluster restoration.
  • Cluster restoration interrupts services for a short period of time. The interruption duration depends on the service volume. You are advised to perform this operation during off-peak hours.
  1. Log in to the GaussDB(DWS) console.
  2. Choose Dedicated Clusters > Clusters and locate the cluster whose load is unbalanced.
  3. In the Cluster Status column of the cluster, click Fix under Unbalanced.

  4. In the dialog box that is displayed, confirm that the service is in off-peak hours, and click Yes. A message will be displayed in the upper right corner, indicating that the switchback request is being processed.
  5. Check the cluster status. During the switchback, the cluster status is Switching back. After the switchback, the cluster status will change to Available.
Parent topic: GaussDB(DWS) Cluster O&M
<script language="JavaScript"> </script>