Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for ClickHouse®
  • Getting started
    • Resource relationships
    • Host classes
    • Networking in Managed Service for ClickHouse®
    • Quotas and limits
    • Storage
    • Backups
    • Replication
    • Dictionaries
    • Sharding
    • Service users
    • Maintenance
    • Supported clients
    • Memory management
    • ClickHouse® versioning policy
    • ClickHouse® settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Yandex Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Quotas and limits

Quotas and limits in Managed Service for ClickHouse®

Written by
Yandex Cloud
Improved by
amatol
Updated at October 30, 2025

Managed Service for ClickHouse® has the following limits:

  • Quotas are organizational constraints that can be changed by support on request.
  • Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

If you need more resources, you can increase your quotas in one of the following ways:

  • Make a request to increase your quotas.
  • Contact support and specify which quotas you want increased and by how much.

To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g., editor or admin.

You can manage your quotas with Cloud Quota Manager.

QuotasQuotas

Type of limit

Value

Number of clusters per cloud
mdb.clusters.count

16

Total number of processor cores for all database hosts per cloud
mdb.cpu.count

64

Total virtual memory for all database hosts per cloud
mdb.memory.size

512 GB

Total storage capacity for all clusters per cloud
mdb.ssd.size

4,096 GB

LimitsLimits

Type of limit Minimum value Maximum value
Host class b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) m3-c80-m640 (80 vCPU Intel Ice Lake, 640 GB RAM)
Number of ClickHouse® hosts per non-sharded cluster when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) 1 7
Number of ClickHouse® hosts in a non-sharded cluster when using non-replicated SSD storage 3 7
Number of ClickHouse® hosts in a non-sharded cluster when using local SSD storage 2 7
Number of shards in a sharded cluster 1 50
Number of hosts per shard when using an HDD or SSD network storage or an ultra high-speed network storage with three replicas (SSD) 1 7
Number of hosts in a shard when using non-replicated SSD storage 3 7
Number of hosts in a shard when using local SSD storage 2 7
Total number of hosts per cluster 1 353 (50 shards × 7 hosts + 3 ZooKeeper hosts)
Amount of data per host when using network HDD or SSD storage (for Intel Broadwell and Intel Cascade Lake) 10 GB 4,096 GB
Amount of data per host when using network HDD or SSD storage (for Intel Ice Lake) 10 GB 8,192 GB
Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network storage with three replicas (SSD) 93 GB 16,368 GB
Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) 100 GB 1,500 GB
Amount of data per host when using local SSD storage (for Intel Ice Lake) 368 GB 5888 GB
Number of databases per cluster 1 1000

Limits on the maximum number of objectsLimits on the maximum number of objects

The limits on the maximum number of objects in a cluster have two threshold values:

  • Soft limit: When reached, the system.warnings system table will display a warning.

  • Hard limit: When reached, creating new objects of this type will end with an error message.

    Note

    The hard limit threshold only works in ClickHouse® 25.2 and higher.

Type of limit Soft limit Hard limit
Number of databases 500 1000
Number of tables 5000 10000
Number of views 5000 10000
Number of external dictionaries 500 1000

All limits are implemented based on ClickHouse® server settings. You cannot change them.

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Networking in Managed Service for ClickHouse®
Next
Storage
© 2025 Direct Cursus Technology L.L.C.