Creating a DWS Storage-Compute Coupled Cluster

To use Huawei Cloud DWS, create a data warehouse cluster first. When you create a data warehouse cluster, the yearly/monthly billing mode is used by default, which is more favorable than the pay-per-use billing mode. You can customize the computing resources and storage space of the cluster. If you select the pay-per-use mode, nodes will be billed by actual duration of use, with a billing cycle of one hour. This mode is flexible. You can enable or disable the service whenever you like.

This section describes how to create a data warehouse cluster on the DWS console.

Notes and Constraints

You are advised not to use clusters with low specifications, such as clusters with 16 GB memory and 4 vCPUs, in the production environment. Otherwise, resource overload may occur.
To ensure load balancing and high availability for the cluster and prevent service interruptions, you are not advised to connect services directly to a single CN. Instead, configure load balancing to balance the connection to each CN.
The DWS clusters under the same account are physically isolated and cannot share data.
To ensure stable service running, read Before You Start: Performance Management Requirements and Before You Start: High Availability and Reliability Requirements after creating a cluster.

Preparations Before Creating a Cluster

Evaluate the flavor of cluster nodes.
You can select the number of nodes by data volume, service load, and performance. More nodes bring you stronger storage and compute capabilities.

When first using DWS, you can create a cluster with a smaller flavor. Then, you can adjust the cluster scale and node flavor based on the data volume and service load changes without interrupting services. For details, see Scaling Out a Cluster.
Determine the number of nodes that can be used by users.
The number of available nodes is determined by the product type you select, and there must be at least three available nodes. Otherwise, the system displays a message indicating that the cluster cannot be created.

If you have yearly/monthly nodes that meet service requirements, you are advised to use these nodes first to save costs. You can select Yearly/Monthly for Billing Mode.

If the number of requested nodes, vCPU (cores), or memory (GB) exceed the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the detailed remaining quota and the current quota application. You can click Increase quota in the warning dialog box to submit a service ticket and apply for higher node quota. Once approved, we will update your resource quota accordingly and send you a notification. For details, see Quotas.

Procedure

Go to the page for creating a DWS cluster. Configure the DWS cluster information as prompted.
Configure the cluster, including Basic Configuration, Specifications Configuration, Network, EIP, and ELB, Cluster Management, and Database Management, Database Encryption, and More Configurations.
Select a billing mode. If you select the yearly/monthly mode, you also need to configure the service duration. For details, see Yearly/Monthly Subscription.
In the Configuration Summary area on the right, confirm the configurations and click Buy Now. If you select the yearly/monthly billing mode, you will be redirected to the payment page after clicking Buy Now.
After the submission is successful, the creation starts. Click Back to Cluster List. The cluster management page is displayed. The initial status of the cluster is Creating. The cluster creation takes some time. Clusters in the Available state are ready for use.

For how to set the parameters in this area, see Table 1.

**Table 1** Basic parameters
Parameter	Description	Precaution	Example Value
Region	Select the AZ for the cluster nodes to run.	For more information about regions, visit Regions and Endpoints.	-
Billing Mode	Select a billing mode as required. For details, see Billing Description. Yearly/Monthly: This mode allows you to pay for services upfront before using them, ideal for users who prefer not to make advance payments or long-term commitments. Pay-per-use: In this mode, you only pay for what you use, right down to the minute. This is perfect for users who want to avoid upfront payments and long-term commitments.	-	Yearly/Monthly
AZ	You can select one AZ or multiple AZs (select three AZs from the drop-down list). For more information, see Regions and AZs.	Multi-AZ clusters are supported only by clusters of version 8.2.0.100 or later. For a multi-AZ cluster, only three AZs can be selected at a time so far. Server nodes are evenly distributed among the three AZs. The number of nodes in a multi-AZ cluster must be an integer multiple of 3. In a multi-AZ cluster, the number of DNs must be less than or equal to 2.	AZ1

For how to configure specifications parameters, see Table 2.

**Table 2** Parameters for configuring specifications
Parameter	Description	Precaution	Example Value
Version	Product type. It can be: Coupled storage and compute: This type of data warehouse provides enterprise-level data warehouse services with high performance, high scalability, high reliability, high security, low latency, and easy O&M. It is capable of data analysis at a scale of 2,048 nodes and 20 petabytes of data and is suitable for converged analysis services that integrate databases, warehouses, marts, and lakes. Decoupled storage and compute: The storage-compute decoupled data warehouse is designed with a cloud native architecture that separates storage and compute. It also features hierarchical auto scaling for compute and storage, as well as shared storage for virtual warehouses. These capabilities allow for compute isolation and concurrent expansion to handle varying loads, making it an ideal choice for OLAP analysis scenarios.	-	Coupled storage and compute
Storage Type	It can be: Cloud SSD Local SSD	Local SSD disks do not support disk scale-out. For more information, see Disk Types and Performance.	-
Node Flavor	Select the desired node flavor based on service requirements. The node flavor list displays the CPU architecture, vCPUs, memory, compute type, and deployment type of node of each flavor.	For more information about the node flavors supported by DWS and their prices, see the DWS pricing details. For details about the node flavors supported by DWS, see Data Warehouse Specifications. The x86 and Kunpeng architectures differ only in their underlying structure, which is not sensible to the application layer. Both architectures use the same SQL syntax. If you need to create a cluster and find that x86 servers are not enough, you can opt for the Kunpeng architecture.	dws.dc.4xlarge
Hot storage	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. The storage space must be an integer multiple of 100. 200 GB per node is the actual storage capacity for service data. For example, if the number of nodes is set to 3, the total resource capacity is 600 GB. By default, tablespaces are automatically created when you configure cold and hot data storage. You do not need to manually create tablespaces. This feature is supported only in clusters of 8.1.3 and later versions.	-
Nodes	Specify the number of nodes in the cluster. The number of nodes ranges from 3 to 1,024.	The number of nodes in a new cluster cannot exceed the quota that can be used by a user or 1,024. Click Increase quota to submit a service ticket and apply for higher node quota if the node quota is insufficient.	3

Table 3 lists the network, EIP, and ELB parameters.

**Table 3** Network, EIP, and ELB parameters
Parameter	Description	Precaution	Example Value
VPC	Specify a virtual private network for nodes in a cluster to isolate networks of different services. 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. 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.	You can create a share to share VPC resources with other members. After responding to a resource sharing invitation, the members can select the shared VPC resources. For details, see How Do I Use VPC Sharing to Process DWS Resources? For how to create a VPC, see Creating a VPC in the Virtual Private Cloud User Guide.	vpc-dws
Subnet	Specify a VPC subnet. A subnet provides dedicated network resources that are isolated from other networks, improving network security.	After a cluster is created, the subnet cannot be modified. If you need to modify the subnet, you can restore the snapshot of the cluster to a new cluster. The data of the new cluster is the same as that of the old cluster, and the subnet can be modified when the new cluster is created.	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 The default option is Automatic creation, which means the system will create a security group automatically if you do not change the setting. 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, and select the created 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. For details, see Adding 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. For better network performance, do not select 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 Buy now or Specify. If you select Buy now, 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 Create EIP to apply for an EIP. By default, EIP is not selected.	In yearly/monthly billing mode, you cannot buy an EIP during cluster creation. If you use the EIP binding function for the first time in each project of each region, the system prompts you to create the DWSAgencyAccess 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 Huawei Cloud accounts or users with Security Administrator permissions can query and create agencies. By default, the IAM users in those Huawei 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. For details, see Allowing DWS to Manage Resources. 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 public network, bind an EIP to the cluster and create a public network domain name. For details, see Creating a Public Network Domain Name. If DWS is used for the production environment, the new DWS cluster needs to be bound to ELB and then to EIP. Select Do not use here.	-
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. If DWS is used in the production environment, first bind it to ELB, and then bind it to an EIP on the ELB page.	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. Currently, ELBs can be bound in the same VPC or across VPCs.	-

For how to set the parameters in this area, see Table 4.

**Table 4** Cluster management parameters
Parameter	Description	Precaution	Example Value
Cluster Name	Set the name of the data warehouse cluster.	Enter 4 to 64 characters. Only letters (case-insensitive), digits, hyphens (-), and underscores (_) are allowed. The name must start with a letter.	DWS-demo
Cluster Version	Displays the version of the database instance installed in the cluster. The example version number is for reference only.	-	-
Time Zone	You can set the time zone for the tenant cluster, including the system OS time zone and cluster data warehouse time zone.	-	-
Enterprise Project	Enterprise project of the cluster. This parameter is available only to users who have enabled the enterprise project management service. An enterprise project facilitates project-level management and grouping of cloud resources and users. You can select the default enterprise project default or other existing enterprise projects. To create an enterprise project, log in to the EPS console. For details, see the Enterprise Management User Guide.	-	default
Tags	Tags are key-value pairs used to identify clusters. You can click +Add to add tags to the cluster. By default, no tag is added to the cluster. For details about tags, see Overview. Tag key: Enter a tag key name in the text box or select a predefined tag key and an existing resource tag key from the drop-down list. The tag key can contain a maximum of 128 characters. It cannot be an empty string, cannot start with _sys_, and cannot start or end with a space. Only letters, digits, spaces, and the following special characters are allowed: _ . : = + - @ Tag value: Enter a tag value in the text box or select a predefined tag value and an existing resource tag value from the drop-down list. The tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and underscores (_) are allowed. : = + - @	If your organization has configured DWS tag policies, you need to add tags to clusters based on the tag policies. If a tag does not comply with the tag policies, cluster creation may fail. Contact the administrator to learn more about tag policies. A key must be unique in a given cluster. To add a predefined tag, you need to create one on TMS and then select it from the Tag key drop-down list. You can click Create Predefined Tags to go to the Predefined Tags page of the TMS console. Then, click Create Tag in the upper corner of the page to create a predefined tag.	-

The default database is set to gaussdb (which cannot be changed). Table 5 lists the database management, database encryption, and more configurations.

**Table 5** Database management, database encryption, and more configurations
Parameter	Description	Precaution	Example Value
Administrator Account	Set the database administrator name.	The administrator username must: Consist of lowercase letters, digits, or underscores. Start with a lowercase letter or an underscore. Contain 6 to 64 characters. The username cannot be a keyword of the DWS database. For details about the keywords of the DWS database, see Keyword.	dbadmin
Administrator Password	Set the password of the database administrator account. Change the password regularly and keep it secure.	The password must: Consist of 12 to 32 characters. Not be the username or the username spelled backwards. Contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!?, .:;_(){}[]/<>@# %^&*+\|\=-) Pass the weak password check.	-
Confirm Password	Enter the database administrator password again.	-	-
Database Port	Specify the port used when the client or application connects to the database in the cluster. The port number ranges from 8000 to 30000.	The database port of a created cluster cannot be changed. You can specify the database port only when creating a cluster.	8000
Encrypt DataStore	If this function is enabled, Key Management Service (KMS) encrypts the cluster and the cluster's snapshot data. For clusters running 9.1.1.200 and later versions, you can select the encryption level (cluster-level or table-level). The function depends on KMS authorization instead of tenant agencies. Method 1: Select a key name. You can create a resource share to share KMS resources with other members. After accepting the sharing invitation, members can select the shared KMS resource from the key source. Method 2: Enter the key ID. Enter the key ID used for authorizing the current tenant. For details, see Viewing a CMK. When you grant permissions on the Creating a Grant page, the authorized object must be an account instead of a user. The authorized operations must at least contain Querying key details, Encrypting data, and Decrypting data.	If no KMS key is available, log in to KMS and create one. For details, see Data Encryption Workshop User Guide. Only users with the Tenant Admin permission can view and toggle the Encrypt DataStore switch. By default, only Huawei Cloud accounts or users with Security Administrator permissions can query and create agencies. IAM users under an account do not have the permission to query or create agencies by default. Contact a user with that permission and complete the authorization on the current page. For details, see Allowing DWS to Manage Resources. If you have not created an agency, the system displays a dialog box asking you to create the DWSAgencyAccess agency and delete the agency with the highest permissions when you enable database encryption for the first time. Click OK to create an agency and grant DWS the permissions to access KMS. Select the created KMS key from the KMS Key Name drop-down list. The database encryption function cannot be disabled once it is enabled. After Encrypt DataStore is enabled, the key cannot be disabled, deleted, or frozen when being used. Otherwise, the cluster becomes abnormal and the database becomes unavailable. After database encryption is enabled, you cannot use open APIs to restore created snapshots.	-
More Configurations	CNs: CNs, or Coordinators, receive access requests from the clients and return the execution results. They also split and distribute tasks to the data nodes (DNs) for parallel execution. In a large-scale cluster, you are advised to deploy multiple CNs. Backup Device: The system automatically creates snapshots at the preset time and interval. For details, see Table 6. IPv6 CIDR Block: Specify whether to enable the IPv6 dual stack for the cluster. If IPv6 is selected, a client or application can connect to the database using an IPv6 address.	Number of deployed CNs. The value ranges from 3 to the number of cluster nodes. The maximum value is 20 and the default value is 3. To enable IPv6, ensure that the following conditions are met: The subnet configured in Table 3 is an IPv6 dual-stack subnet. The cluster supports IPv6 addresses and a maximum of three NICs. The cluster version must be 8.2.1.210 or later.	-

**Table 6** Backup device parameters
Parameter	Description
Backup Device	Select OBS or NFS from the drop-down list.
NFS Backup File System Address (NFS)	NFS shared IP address. To mount the SFS shared path, enter its IP address. If successful, a mount directory will be created in the /var/chroot/nfsbackup directory of the cluster instance.

**Table 7** Duration
Parameter	Description
Required Duration (Yearly/Monthly)	Configure the required duration. You get a greater discount if you purchase a longer period. Price is displayed at the bottom of the page for your reference. You can click Pricing details to view the detailed price.
Auto-renewal (Yearly/Monthly)	By default, this option is not selected. Renewal rules: If you select one month to nine months, your monthly package will be renewed for a month upon expiration. If you select a yearly package, it will be renewed for one year upon expiration. Example: Customer A purchases a cluster in yearly/monthly mode and select enables auto-renewal. If the cluster is subscribed to for eight months, it will be automatically renewed each month. If the cluster is subscribed to for two years, it will be automatically renewed each year. For details about the renewal fee deduction, see Fee Deduction Rules.

Handling the Cluster Creation Failure

If the cluster fails to be created, you can go to the DWS console and choose Cluster > Cluster List to view the cluster status and the cause of the creation failure.

Viewing the Cause of a Creation Failure

Log in to the DWS console.
In the navigation pane on the left, choose Cluster > Cluster List.
In the cluster list, locate the cluster whose Cluster Status is Creation failed.
Click View Details in the Cluster Status column to view the cause of the cluster creation failure.

If the fault persists, contact technical support.

Deleting a Cluster That Fails to Be Created

You can delete a cluster that fails to be created if you do not need it. Before deletion, check the cause of creation failure.

Log in to the DWS console.
In the navigation pane on the left, choose Cluster > Cluster List.
In the cluster list, locate the row containing the failed cluster to be deleted, click More in the Operation column, and select Delete.
In the displayed dialog box, confirm the deletion.
After confirming that the information is correct, enter DELETE or click Auto Enter and click OK to delete the cluster. The cluster status in the cluster list will change to Deleting and the cluster deletion progress will be displayed.

When you delete a cluster, its automatically created security group is also deleted, as long as other clusters are not using it.

Parent Topic: Creating a Dedicated DWS Cluster

Previous topic: Creating a Dedicated DWS Cluster

Next topic: Creating a DWS Storage-Compute Decoupled Cluster