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 StoreDoc
  • Getting started
    • Resource relationships
    • Networking in Yandex StoreDoc
    • Quotas and limits
    • Storage in Yandex StoreDoc
    • Backups
    • Replication and fault tolerance
    • Sharding
    • Users and roles
    • Maintenance
    • Supported clients
    • Yandex StoreDoc settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Quotas and limits

Yandex StoreDoc quotas and limits

Written by
Yandex Cloud
Improved by
amatol
Updated at November 26, 2025

Yandex StoreDoc has the following limitations:

  • 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

Number of GPUs
mdb.gpu.count

0

LimitsLimits

Type of limit Minimum value Maximum value
Host class b1.medium (2 × 50% vCPU Intel Broadwell, 4 GB RAM) m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 GB RAM)
Number of shards per cluster 1 10
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 storing data on non-replicated or local SSDs* 3 7
Number of hosts per cluster 1 or 3 hosts depending on the disk type; the cluster is created in an unsharded state. 70 (10 shards, 7 hosts)
Amount of data on the host when using network HDD or SSD storage 10 GB 2,048 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 2,232 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

* Read more on how platform selection affects available storage types.

The maximum available number of simultaneous connections to a single Yandex StoreDoc cluster host depends on the amount of RAM on the host:

Amount of RAM Maximum number of connections
2 GB 2048
4 GB 4096
8 GB 8192
16 GB or higher 16 384

Was the article helpful?

Previous
Networking in Yandex StoreDoc
Next
Storage in Yandex StoreDoc
© 2025 Direct Cursus Technology L.L.C.