Manage your Managed ClickHouse® service
Day-to-day operations on a Managed ClickHouse® service.
Prerequisites
- Exoscale CLI version 1.100.0 or later. Earlier releases don’t
support ClickHouse in the
exo dbaascommands.
Note
exo dbaas update and exo dbaas delete ask for a confirmation, which -f skips.
Applying maintenance updates on demand has no exo dbaas equivalent and uses exo x,
the API passthrough.
Inspect a service
Read the service description, including its state, plan, version, IP filter, components and users:
exo dbaas show my-clickhouse -z ch-gva-2Add --backups to list the backups, or --settings clickhouse to read the service
settings. For scripts, -O json returns the same details as JSON.
Monitor a service
Expose your service metrics to your own monitoring stack with an external endpoint. See Managed ClickHouse® metrics available via Prometheus and Managed ClickHouse® metrics available via Datadog.
Query level statistics are available in the service itself, see Fetch query statistics.
Resize a service
Change the plan of a running service to add capacity. See Scaling a managed service:
exo dbaas update my-clickhouse -z ch-gva-2 -f --plan startup-32Schedule maintenance updates
Set the weekly window during which Exoscale applies maintenance, giving the day and the time together:
exo dbaas update my-clickhouse -z ch-gva-2 -f \
--maintenance-dow sunday --maintenance-time 04:00:00Apply the pending maintenance updates immediately, without waiting for the next window.
This operation goes through exo x, the API passthrough:
exo x start-dbaas-clickhouse-maintenance my-clickhouse -z ch-gva-2Maintenance replaces the service nodes, so expect a short interruption, longer on single-node plans. Some features expect a fully updated service: for example, all maintenance updates must be applied before you enable tiered storage.
See Maintenance window for the platform behavior.
Fork a service
Create a new service from a backup of an existing one, see Fork and restore from Managed ClickHouse® backups.
Delete a service
If the service is protected against termination, the deletion is refused until you disable the protection. Services created with the CLI are protected by default, see Secure a Managed ClickHouse® service:
exo dbaas update my-clickhouse -z ch-gva-2 -f --termination-protection=false
exo dbaas delete my-clickhouse -z ch-gva-2 -f