Skip to main content

Overview

Once your cluster is deployed, you can access it through the HowClusters totab deployon the left. Here, you will see a new cluster

entry

1) Go towith the Elestioname Clusters tab.

001.png

2) Click on Deploy My First Cluster.

002.png

3) Selectof your Software, for example, MySQL.

003.png

4) Choose your Provider and Service Plan, then click Next.

5) Choose a name for your cluster, for example mysql-cluster

6) On Select Support & advanced setting part, scroll down until Cluster configuration(Optional) part.

Here, you’ll have three configuration options:

  • Single Node
  • Primary/Replica
  • Multi-Master

Single node

004.png

When choosing the Single Node option, you’ll deploy a standalone node for MySQL. This means only one node will be set up, but it will already be configured as a Primary node. This setup ensures that, in the future, if you want to scale by adding one or more nodes, it will be seamlessly possible without requiring reconfiguration.

Primary/Replica

005.png

When choosing the Primary/Replica option, you will deploy at least one Primary node, and you can specify the number of replicas to include in the cluster.

By default, the number of replicas will be determined by the minimum required for the selected software. However, you can increase the number of replicas as long as it fits within your Service Quota.

For example, if you select 3 replicas from the dropdown, your cluster will consist of 4 nodes: 1 Primary and 3 Replicas.

Multi-Master

006.png

When choosing the Multi-Master option, you will deploy 2 Primary nodes that are connected to each other, ensuring mutual synchronization and redundancy.

It’s important to note that not all software supports this option. Make sure to verify compatibility with your selected software before proceeding.

7) Click on Create Service.

Now your cluster will be configured. Depending on the selected software, this process may take a little time.

CNAME

When deploying a new cluster, you will choose a CNAME. In our example, weit usedwill appear as mysql-cluster.cluster.

Each001.png

node

By inclicking on the cluster name, you will inheritaccess the baseOverview nameof your cluster.

The Overview is divided into two parts:

  • Cluster Management Options
  • General informations

 

Cluster Management Options

002.png

 

This section provides tools to manage and receivecontrol ayour number incrementally.

For example, if you deploy a Primary/Replica cluster with 3 nodes, the nodes will be named:cluster:

  • mysql-cluster1Protection: Prevent accidental deletion of your cluster by enabling the lock option.
  • mysql-cluster2
  • mysql-cluster3

These names will also be used for their individual CNAMEs, automatically created by Elestio.

In addition, you will have a CNAME for the base name itself, such as mysql-cluster.

This base CNAME will always point to the PrimaryAdd Node.: If you promoteAdd a new node to Primary,your thecluster. baseAny CNAMEadded node will automatically updatefunction as a replica.

  • Upgrade Plan: Update the support plan for your cluster to reflecthigher levels, such as Level 2 or Level 3.
  • Resync Cluster: If one or more replicas go down, use this option to resynchronize them with the change,primary ensuringnode.
    • seamless
  • Migration: continuitySeamlessly withoutmigrate requiringa reconfigurationdatabase acrossto your services.cluster.
  • Limit Access per IP: Restrict access to your cluster to specific IP addresses for improved security.

    •  

    General Information

    003.png

     

    This section provides key details about your cluster, including:

    • CNAME: The fully qualified domain name for your cluster. In our example: mysql-cluster-u161.vm.appdrag.net.
    • Network: Displays the IP addresses associated with the cluster:
      • IPv4: 159.69.118.15
      • IPv6: 2a01:4f8:c012:915d::/64
      • Global Private IP: 10.19.144.10
    • Deployment Duration: The time taken to deploy the cluster.
    • Project ID: The unique identifier for the project.
    • Cluster ID: The unique identifier for the cluster.
    • Primary Node ID: The ID of the primary node.
    • Service Type: Specifies the type of service.
    • Created By: The creator of the cluster.
    • Creation Time: The date and time the cluster was created.
    Back to top