vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/dws/umn/dws_01_7115.html
Lu, Huayi c5fcb46315 DWS UMN 801 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Lu, Huayi <luhuayi@huawei.com>
Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
2022-12-13 12:47:57 +00:00

9.9 KiB
Raw Permalink Blame History

CNs

Purpose

After a cluster is created, the number of required CNs varies with service requirements. The CN management function enables you to adjust the number of CNs in the cluster. The operations are as follows:

Constraints and Limitations

  • During resource provisioning, the default number of CNs is 3. You can adjust the number of CNs based on the number of provisioned nodes. The number of CNs ranges from 2 to 20.
  • Do not perform other O&M operations when adding or deleting a CN.
  • Stop services when adding or deleting a CN.
  • If a fault occurs when you add or delete a CN and the rollback also fails, log in to the background to rectify the fault. For details, see .

Adding CNs

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the cluster to which you want to add CNs.
  3. In the Operation column of the specified cluster, choose More > Manage CN > Add CN Node.

  4. On the displayed page, set the number of CNs as required and click OK.

    • Before adding a CN, ensure that the cluster is in the Available, Unbalanced, or Redistributing state.
    • The number of CNs after adjustment must be greater than the number of deployed CNs, less than or equal to the number of nodes, and less than or equal to 20.

Deleting CNs

  1. Log in to the GaussDB(DWS) management console.
  2. On the Clusters page, locate the cluster from which you want to delete CNs.
  3. In the Operation column of the specified cluster, choose More > Manage CN > Delete CN Node.

  4. On the displayed page, select the CN to be deleted and click OK.

    • At least one CN must be reserved when you delete a CN.
    • When you delete a CN, the cluster must be in the Available, Degraded, or Unbalanced state.
    • If an elastic IP address has been bound to a CN, the CN cannot be deleted.
    • If abnormal nodes exist, only the abnormal CNs can be deleted.
      • If one CN is faulty, only this CN can be deleted.
      • If two or more CNs are faulty, no CN can be deleted.

Parent topic: Cluster HA