Aiven for ClickHouse® limits and limitations
This article covers quotas for the Aiven for ClickHouse® service and restrictions on its use. This information helps you make right choices when working with Aiven for ClickHouse, for example, on your infrastructure design, tools, modes of interactions, potential integrations, or handling concurrent workloads.
Limitations
From the information about restrictions on using Aiven for ClickHouse, you can easily draw conclusions on how to get your service to operate closer to its full potential. Use Recommended approach as guidelines on how to work around specific restrictions.
Name | Description | Recommended approach |
---|---|---|
Backups - one snapshot a day | Since Aiven for ClickHouse service takes a single snapshot a day only:
| |
Service integrations | You can integrate your Aiven for ClickHouse service with PostgreSQL® and Kafka® only. | - |
Table engines availability |
|
|
Cloud availability | Available on AWS, GCP, and Azure only | Use the available cloud providers. |
Kafka Schema Registry | Aiven for ClickHouse doesn't support Kafka Schema Registry, which allows to build stream processing pipelines with schemas. | - |
Querying all shards at once | If you have a sharded plan, you must use a distributed table on top of your MergeTree table to query all the shards at the same time, and you should use it for inserts too. | Use a distributed table with sharded plans. Check Query data across shards for the instructions. |
ON CLUSTER queries | Aiven for ClickHouse doesn't support ON CLUSTER queries because it actually runs each data definition query on all the servers of the cluster without using ON CLUSTER. | Run queries without |
Creating a database using SQL | You cannot create a database directly using SQL, for example, if you'd like to add a non-default database. | Use the Aiven's public API. |
Scaling down the number of nodes | You only can scale up the number of nodes in a cluster. | - |
Limits
Service limits are determined by a plan that this service uses.
Plan | VMs | CPU per VM | RAM per VM | Total storage |
---|---|---|---|---|
Hobbyist | 1 | 1 (2 for AWS only) | 4 GB | 180 GB |
Startup | 1 | 2 | 16 GB | 1150 GB |
Business | 3 | 2 - 8 | 16 - 64 GB | 1150 - 4600 GB |
Premium | 6 - 30 | 2 - 8 | 16 - 64 GB | 2300 - 46000 GB |
If you need a custom plan with capacity beyond the listed limits, contact us.