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 Studio
    • 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 YTsaurus
  • Getting started
    • Quotas and limits
    • Configuration options for cluster components
  • Access management
  • Pricing policy

In this article:

  • Quotas
  • Limits
  • Component configuration limits
  • Storage limits
  1. Concepts
  2. Quotas and limits

Quotas and limits in Managed Service for YTsaurus

Written by
Yandex Cloud
Updated at August 7, 2025
  • Quotas
  • Limits
    • Component configuration limits
    • Storage limits

Note

The service is at the Preview stage.

Managed Service for YTsaurus 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

5

Total number of processor cores for all cluster components per cloud

300

Total HDD storage capacity

18,432 GB

Total virtual memory for all cluster components per cloud

762 GB

Total non-replicated SSD storage capacity

5,022 GB

Total SSD storage capacity

5,022 GB

LimitsLimits

Component configuration limitsComponent configuration limits

Exec nodesExec nodes

Type of limit Minimum value Maximum value
Number of exec nodes per cluster 1 1,000
Exec node class c8-m32 (8 vCPUs, 32 GB RAM) c80-m640 (80 vCPUs, 640 GB RAM)
HDD storage size 10 GB 102,400 GB
SSD storage size 10 GB 102,400 GB
Non-replicated SSD storage size 93 GB 102,393 GB

Tablet nodesTablet nodes

Type of limit Minimum value Maximum value
Number of tablet nodes per cluster 0 1,000
Tablet node class c8-m16 (8 vCPUs, 16 GB RAM) c32-m64 (32 vCPUs, 64 GB RAM)

HTTP proxiesHTTP proxies

Type of limit Minimum value Maximum value
Number of HTTP proxies 1 10

RPC proxiesRPC proxies

Type of limit Minimum value Maximum value
Number of RPC proxies 1 10

Storage limitsStorage limits

HDD storageHDD storage

Type of limit Minimum value Maximum value
Number of disks 3 600
Disk size 10 GB 102,400 GB

SSD storageSSD storage

Type of limit Minimum value Maximum value
Number of disks 3 600
Disk size 10 GB 102,400 GB

Non-replicated SSD storageNon-replicated SSD storage

Type of limit Minimum value Maximum value
Number of disks 3 600
Disk size 93 GB 102,393 GB

Was the article helpful?

Previous
Deleting a cluster
Next
Configuration options for cluster components
© 2025 Direct Cursus Technology L.L.C.