Creating a DWS Storage-Compute Decoupled Cluster

Region

Select the AZ for the cluster nodes to run.

For more information about regions, visit Regions and Endpoints.

-

AZ

You can select one AZ or multiple AZs (select three AZs from the drop-down list).

For more information, see How Do I Select a DWS Region and AZ?.

AZ1

Version

The options are as follows:

Decoupled storage and compute: This type of data warehouse is designed with a cloud native architecture that separates storage and compute. It also features hierarchical auto scaling for computing and storage, as well as multi-logical cluster shared storage technology (Virtual Warehouse or VW). These capabilities allow for computing isolation and concurrent expansion to handle varying loads, making it an ideal choice for OLAP analysis scenarios.

-

Node Flavor

Select a node flavor. The node flavor list displays the CPU architecture, vCPUs, memory, compute type, and deployment type of node of each flavor.

-

Hot Storage (with Cache)

Available storage capacity of each node.

• The storage capacity you apply for has the necessary file system overhead, which includes index nodes and the space required for database running. If the idle space is less than 100 GB, scale-out may fail due to insufficient space.
• The displayed 200GB/node includes the storage for cache. For example, if you create 3 nodes, each having 200 GB capacity, the total resource capacity is 600 GB, and the actual storage space available to you is 300 GB.

-

Cold Data

Store data in separate OBS buckets.

-

Nodes

Specify the number of nodes in the cluster.

The number of nodes ranges from 3 to 256.

3

VPC

Specify a VPC to isolate the cluster's network.

• If you are creating your first DWS cluster and have not configured a VPC, click Create VPC to go to the VPC console and create a VPC that meets your requirements.

  For details about how to create a VPC, see "VPC and Subnet > Creating a VPC" in the Virtual Private Cloud User Guide.

• After selecting a VPC from the drop-down list, you can click Create VPC to go to the VPC console to view details about the selected VPC.
• You can click to refresh the options in the VPC drop-down list.

-

vpc-dws

Subnet

Specify a VPC subnet.

A subnet provides dedicated network resources that are isolated from other networks, improving network security.

Once a cluster is created, its subnet cannot be changed. To update the subnet, restore the cluster's snapshot into a new cluster. The new cluster will have identical data, and you can adjust the subnet during its creation.

subnet-dws

Security Group

Specify a VPC security group.

A security group restricts access rules to enhance security when DWS and other services access each other.

• Automatic creation

  If Automatic creation is selected, the system automatically creates a default security group. This option is selected by default.

  The rule of the default security group is as follows: The outbound allows all access requests, while the inbound is open only to the database port that you set to connect to the DWS cluster.

  The format of the default security group's name is dws-<cluster name>-<database port of the DWS cluster>, for example, dws-dws-demo-8000.

• Manual creation

  You can also log in to the VPC management console to manually create a security group. Then, go back to the page for creating DWS clusters, click next to the Security Group drop-down list to refresh the page, and select the new security group.

  To enable the DWS client to connect to the cluster, add an inbound rule to the new security group to allow access to the DWS cluster's database port. The following is an example of an inbound rule.

  • Protocol: TCP.
  • Port: 8000. Use the database port set when creating the DWS cluster. This port receives client connections to DWS.
  • Source: Select IP address and use the host IP address of the client host, for example, 192.168.0.10/32.

• If the quotas of the security group and the security group rule are insufficient, an error message will be displayed after you submit the cluster creation application. You can select an existing group and retry.
• After a DWS cluster is created, you can change the security group. You can also add, delete, or modify security group rules in the current security group. For details, see "Modifying a Security Group". Changing the security group of a cluster may cause brief service disruption. Exercise caution when performing this operation. To improve network performance, limit your selection to no more than five security groups.

Automatic creation

EIP

Whether users can use a client to connect to a cluster's database over the Internet.

• If you select EIP, you can select Automatically assign or Specify. If you select Automatically assign, the system automatically assigns an EIP with dedicated bandwidth to the cluster. You can set the bandwidth as needed. If you select Specify, you can bind an existing EIP to the cluster. If no EIP is available in the drop-down list, click Assign EIP to apply for an EIP.
• By default, EIP is not selected.

• If you use the EIP binding function for the first time in each project of each region, the system prompts you to create the DWSAccessVPC agency to authorize DWS to access VPC. After the authorization is successful, DWS can switch to a healthy VM when the VM bound with the EIP becomes faulty.
• By default, only cloud accounts or users with Security Administrator permissions can query and create agencies. By default, the IAM users in those cloud accounts cannot query or create agencies. When the users use the EIP, the system makes the binding function unavailable. Contact a user with the DWS Administrator permissions to authorize the agency on the current page.
• Do not use indicates disabling access to the cluster over the public network. After a cluster is created, if you want to access it over the Internet, bind an EIP to the cluster and create an Internet domain name. For details, see Creating a Public Network Domain Name.

-

ELB

Whether ELB is bound. With ELB health checks, CN requests of a cluster can be quickly forwarded to normal CNs. If a CN is faulty, the workload can be immediately shifted to a healthy node, minimizing cluster access faults.

• By default, ELB is selected. You can bind a specified load balancer to the cluster. If no available load balancers are displayed in the drop-down list, click Create ELB to go to the ELB page and create one as needed.

• If you deselect ELB, ELB is not used.

Configure load balancing to ensure load balancing and high availability of the cluster and prevent service interruptions. You are not advised to directly connect services to a single CN.

-