Create a Cluster
This article explains how to add a new cluster in a native cloud deployment on AWS.
By default, each database has a main cluster. In a native cloud deployment, you can add additional worker clusters for higher concurrency. Each worker cluster must have the same number of nodes as the main cluster.
This procedure modifies or creates resources in your cloud account. Make sure that you do not exceed any resource limits set by your organization by carrying out this procedure.
Prerequisites
The database access node must be running.
Set the config path
When you make changes to an existing deployment you must use the same configuration that was used when creating the deployment. If the configuration file that was used is not named config
and/or is not located in the current working directory (on the host where you run c4), you must prepend the c4 commands with the path to the configuration file using CCC_CONFIG=<path-to-config>
.
Example:
CCC_CONFIG=./path_to_config/my_config c4 <command>
In the following examples, the default configuration file is used.
Procedure
This procedure uses the c4 and confd_client command-line tools in a Linux terminal. For more information about these tools, see Exasol Deployment Tool (c4) and ConfD.
If the worker cluster is created while the database is stopped, it will not start automatically. To learn how to manually start the cluster, see Start a Cluster.
Step 1: Connect to COS
Connect to the cluster operating system (COS) using c4 connect -i PLAY_ID -s cos
.
Example:
./c4 connect -i c3275f84 -s cos
For more information about how to use c4 connect
, see How to use c4.
Step 2: Create a new worker cluster
To create a new worker cluster, use the ConfD job infra_worker_db_add with the following parameters:
Parameter name | Data type | Description |
---|---|---|
master_db_name | string | The name of the main cluster |
new_worker_db_name | string | The name for the new worker cluster |
instance_type | string | Enter the instance type for the nodes in the new cluster |
This job will create a new worker cluster in the deployment with the same number of nodes as the main cluster.
To get the name of the main cluster, you can use the ConfD job infra_overview_get.
Example:
confd_client infra_overview_get
...
cluster_id: 0
databases:
MY_DATABASE:
...
name: MY_DATABASE
confd_client infra_worker_db_add master_db_name: MY_DATABASE new_worker_db_name: MY_WORKER_CLUSTER instance_type: r5d.2xlarge
Step 3: Disconnect from COS
To disconnect from COS, use Ctrl-D.
Verification
To verify that the new nodes are running, use c4 ps
.