Adding subclusters in MC

You can add a subcluster to an Eon Mode database on-premises or in the cloud, to provide your database with more compute power, and to separate workloads.

You can add a subcluster to an Eon Mode database on-premises or in the cloud, to provide your database with more compute power, and to separate workloads.

For more information about the rules governing subclusters, see Subclusters.

Adding a subcluster on a cloud platform

When you use MC to add an Eon Mode subcluster on a cloud platform, MC provisions the requested instances, configures them as nodes in your database cluster, and forms those nodes into a new subcluster.

You can add a second primary subcluster in order to stop the original primary. Be sure to make the replacement primary subcluster at least one node larger than the original. (If you make them the same size, they both count equally toward the quorum, and stopping either would violate the quorum, so you cannot stop either one. For more information, see Data integrity and high availability in an Eon Mode database.)

Amazon Web Services (AWS)

The following steps add a subcluster on AWS:

  1. On the Manage > Subclusters tab, click Add Subcluster to open the Add Subcluster window.

  2. On Enter AWS Credentials and preferences, some values might populate based on your current configuration. Accept the defaults or enter the following values:

    • AWS Region: Enter the same region as your cluster.

    • AWS Subnet: The subnet for your cluster. By default, Vertica creates your cluster in the same subnet as your MC instance.

    • AWS Key Pair: Your Amazon key pair for SSH access to EC2 instances.

  3. Select Next. On the Specify Subcluster Information screen, supply the following information:

    • Subcluster Name: Enter a name for your subcluster.

    • Subcluster type from the dropdown list. Select Primary or Secondary.

    • Number of instances in this subcluster: Select the number of nodes that you want in the subcluster. If you are using the free Community Edition license, you are limited to 3 nodes. If you enter a value greater than 3, you are prompted to enter an upgraded license to continue.

    • Vertica License: Click Browse to locate and upload your Vertica license key file.

      If you do not supply a license key file here, the MC uses the Vertica Community Edition license. This license has a three node limit, so the value in Number of instances in this subcluster cannot be larger than 3 if you do not supply a license. See Managing licenses for more information.

    • Node IP setting: Choose a node IP setting. If you choose Public IP, the address is not persistent across instance stop and start.

  4. Select Next. On the Specify cloud instance and data storage info screen, Database Depot Path is populated to match the original cluster configuration. Choose or enter a value in the following:

    • EC2 Instance Type: For recommended instance types, see Choosing AWS Eon Mode Instance Types. For a comprehensive list of Vertica supported instance types, see Supported AWS instance types.

    • Database Depot Path: This field is populated with the existing subcluster's depot path.

    • EBS Volume Type: This field is populated with the volume configuration defaults for the associated instance type. Select a new value to change the default.

    • EBS Volume Size (GB) per Volume per Available Node: This field is populated with the volume configuration defaults for the associated instance type. Enter a new value to change the default.

  5. Select Next. On the Specify additional storage and tag info screen, the following fields are populated:

    • Database Catalog Path: The path to a persistent storage location.

    • Database Temp Path: The path to an ephemeral storage location if the node instance type includes the ephemeral storage option.
      Under each path, there are EBS Volume Type and EBS Volume Size (GB) per Volume per Available Node fields that are populated with volume configuration defaults for the associated instance type. Select or enter a new value to change the default path.

    • Optionally, select Tag EC2 Instances to assign distinctive, searchable metadata tags to the instances in your new subcluster. Existing tags are displayed.

  6. Select Next. On Review 'Add Subcluster' information, confirm the configuration details for your new subcluster.

  7. Select Add Subcluster to create the subcluster.

After the subcluster is created, The Subcluster page displays. The MC automatically subscribes the nodes in your new subcluster to shards so that the nodes are ready to use.

Google Cloud Platform (GCP)

The following steps add a subcluster on GCP:

  1. On the Manage > Subclusters tab, click Add Subcluster to open the Add Subcluster window.

  2. On Specify Subcluster Information, supply the following information:

    • Subcluster Name: Enter a name for your subcluster.

    • Subcluster type from the dropdown list. Select Primary or Secondary.

    • Number of instances in this subcluster: Select the number of nodes that you want in the subcluster. If you are using the free Community Edition license, you are limited to 3 nodes. If you enter a value greater than 3, you are prompted to enter an upgraded license to continue.

    • Vertica License: Click Browse to locate and upload your Vertica license key file.

      If you do not supply a license key file here, the MC uses the Vertica Community Edition license. This license has a three node limit, so the value in Number of instances in this subcluster cannot be larger than 3 if you do not supply a license. See Managing licenses for more information.

    • Node IP setting: Choose a node IP setting. If you choose Public IP, the address is not persistent across instance stop and start.

  3. Select Next. Cluster configuration might take a few minutes.

  4. On Specify cloud instance and depot storage info, supply the following information:

  5. Select Next. On Specify additional storage and label info, supply the following:

    • Database Catalog Path: The path to a persistent storage location.

    • Disk Type: Volume type for the database catalog.

    • Size (GB) per Available Node: Volume size for the database catalog.

    • Database Temp Path: The path to an ephemeral storage location if the node instance type includes the ephemeral storage option.

    • Disk Type: Volume type for the database temp storage location.

    • Size (GB) per Available Node: Volume size for the database temp storage location.

    • Label Instances: Optional. Assign distinctive, searchable metadata tags to the instances in your new subcluster. Existing tags are displayed.

  6. Select Next. On Review Information, confirm the configuration details for your new subcluster, and accept the terms and conditions.

  7. Select Add Subcluster to create the subcluster.

After the subcluster is created, The Subcluster page displays. The MC automatically subscribes the nodes in your new subcluster to shards so that the nodes are ready to use.

Microsoft Azure

The following steps add a subcluster on Azure:

  1. On the Manage > Subclusters tab, click Add Subcluster to open the Add Subcluster window.

  2. On Specify Subcluster Information, supply the following information:

    • Subcluster Name: Enter a name for your subcluster.

    • Subcluster type from the dropdown list. Select Primary or Secondary.

    • Number of instances in this subcluster: Select the number of nodes that you want in the subcluster. If you are using the free Community Edition license, you are limited to 3 nodes. If you enter a value greater than 3, you are prompted to enter an upgraded license to continue.

    • Vertica License: Click Browse to locate and upload your Vertica license key file.

      If you do not supply a license key file here, the MC uses the Vertica Community Edition license. This license has a three node limit, so the value in Number of instances in this subcluster cannot be larger than 3 if you do not supply a license. See Managing licenses for more information.

    • Node IP setting: Choose a node IP setting. If you choose Public IP, the address is not persistent across instance stop and start.

  3. Select Next. Cluster configuration might take a few minutes.

  4. On Specify cloud instance and depot storage info, supply the following information:

    • Virtual Machine (VM) Size: Select the instance type. For a comprehensive list of Vertica supported instance types, see Recommended Azure VM types and operating systems.

    • Database Depot Path: This value is populated to match the original cluster configuration.

    • Managed Disk Volume Type: Volume type for each node. This value is populated with the volume configuration defaults for the associated instance type.

    • Managed Disk Volume Size (GB) per Volume per Available Node: Volume size for each node. This value is populated with the volume configuration defaults for the associated instance type.

  5. Select Next. On Specify additional storage and label info, supply the following:

    • Database Catalog Path: The path to a persistent storage location.

    • Managed Disk Volume Type: Volume type for the database catalog.

    • Managed Disk Volume Size (GB) per Available Node: Volume size for the database catalog.

    • Database Temp Path: The path to an ephemeral storage location if the node instance type includes the ephemeral storage option.

    • (E16_v4 VMs only) Managed Disk Volume Type: Volume type for the database temp storage location.

    • (E16_v4 VMs only) Managed Disk Volume Size (GB) per Available Node: Volume size for the database temp storage location.

    • Label Instances: Optional. Assign distinctive, searchable metadata tags to the instances in your new subcluster. Existing tags are displayed.

  6. Select Next. On Review Information, confirm the configuration details for your new subcluster.

  7. Select Add Subcluster to create the subcluster.

After the subcluster is created, The Subcluster page displays. The MC automatically subscribes the nodes in your new subcluster to shards so that the nodes are ready to use.

On-premises

For an Eon Mode database on-premises, you can use MC to create additional subclusters. MC displays all available Vertica hosts that are not part of the database. It configures the ones you select to become the nodes in the new subcluster in your database.

  1. On the Manage > Subclusters tab, click Create Subcluster at top left. MC opens the Create Subcluster wizard.

  2. In the first screen, respond in the following fields:

    • **Subcluster Name:**Enter a name for the new subcluster.

    • **Subcluster type dropdown (unlabeled):**Select Primary or Secondary.

    • **Select nodes that will be added to a subcluster:**Select from the list of IP addresses. MC displays all available Vertica hosts within the cluster that are not currently members of a database.

    • **Confirmation:**Click the Confirmation check box to indicate that you want to create the named subcluster, to include the Vertica hosts you selected as nodes.

  3. After you click the Confirmation check box, the Proceed button becomes active. Click Proceed.

MC displays a progress screen while it creates the requested subcluster. Wait for all steps to complete.

See also

Subcluster action rules in MC