Clusters

When creating a cluster, it isn't immediately available upon creation. It will take some time for Kubernetes and the provider to have it ready and running, hence the message: 'Cluster creation in progress.'

Once the cluster is created, you may query the cluster to check that it’s up and running.

Basic cluster information such as Grafana and ClickHouse endpoints, number of rows that have been inserted or cluster disks among many others.

Given a cluster slug, it returns the cluster info.

Stopping a cluster doesn’t delete it. The disks and the data in them will safely be kept (and can be reactivated whenever you need). However the machine itself is stopped so the cluster can no longer ingest data or be queried. This means you will no longer be charged for the machine costs, but you will continue to be charged for the disks as they’re still being kept safe.

Resuming the cluster reactivates the machines attached to the disks. This means you will be able to ingest and query data again (both live and historic). By consequence you will now be charged again for the ongoing machine costs, as well as the disks.

Gigapipe can scale your cluster both horizontally (adding more nodes) and vertically (increase machine power). Scaling the cluster means scaling horizontally by adding more nodes.

Changing the machine type of your cluster allows you to scale vertically (adding more or reducing power per node). You can either increase the power of the machine, or reduce it.

Adding disks to a cluster means adding additional (separate) disks to the cluster. Data can be moved to this disk from the primary disk, or the new disk can be made the primary.

Want to be sure you never run out of space? Apart from setting up disk-autoscaling you can also manually expand a disk.

Want to be sure you never run out of space? We got your back! Disk autoscaling can be enabled at any time in case you forgot or did not want to set up this option when creating the cluster.

Much in the way you can add and edit disk auto-scaling policies, you can also delete them if they’re no longer needed.

Obtain the cost of all your clusters at once.

Provided that the target user belongs to your organization, you can transfer a cluster to them, as long as they have permission to hold it!

You can delete your cluster and all its data at the push of a button. If you think you may need the data again at some point, we suggest having a look at how to temporarily stop a cluster. When a cluster is deleted, the billing is immediately stopped and the organization is not charged for that cluster anymore.

Changing the ClickHouse version of your cluster to stay up to date with the latest releases from ClickHouse.

Seamlessly import your ClickHouse data to an existing Gigapipe cluster

Easily change your table engine to replicated merge tree.