Help Center> GaussDB(DWS)> Management Guide> Managing Logical Clusters> Scheduling GaussDB(DWS) 3.0 Logical Cluster Creation and Deletion
Updated on 2024-06-14 GMT+08:00
View PDF

Scheduling GaussDB(DWS) 3.0 Logical Cluster Creation and Deletion

Context

You can schedule the creation and deletion of logical clusters. Computing logical clusters can be created and deleted during the scheduled period of time to dynamically scale computing resources.

  • This feature supports only GaussDB(DWS) 3.0 clusters. For an earlier version, contact technical support to upgrade it first.
  • In a yearly/monthly GaussDB(DWS) 3.0 cluster, nodes are automatically added when logical clusters are added as scheduled. Nodes are billed on a pay-per-use basis.
  • By default, a logical cluster created using this feature is used to provide computing power. After a user is associated with the logical cluster, the user's queries are processed by this logical cluster, but table creation statements are still processed in the original logical cluster.
  • A user can be bound to only one computing logical cluster.
  • If a user associated with the read-only logical cluster has workloads in progress when the cluster is deleted, an error may be reported.

Procedure

  1. Log in to the GaussDB(DWS) console. In the navigation pane, choose Clusters > Dedicated Clusters.
  2. In the cluster list, click the name of the target cluster. The Cluster Information page is displayed.
  3. After GaussDB(DWS) 3.0 clusters are created, they are in logical cluster mode.

    • GaussDB(DWS) 3.0 cluster: In the navigation pane on the left, switch to the Logical Clusters page, click Add Plan to configure a proper scheduling plan.

  4. Select a plan type. It can be:

    • Periodically: The plan is executed once in every specified period (week or month). A logical cluster is created or deleted as scheduled as long as it does not conflict with other O&M operations.

    • One-time: The plan is executed only once in the specified period.

  5. Click OK. In the scheduled plan list, you can view the plan details and next execution time.

    To avoid affecting services and ensure resources are available at the scheduled time, the plan may be skipped if it conflict with O&M operations, and may be executed about 20 minutes earlier than planned if the cluster creation is time-consuming.