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
    • ML Services
    • 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 Compute Cloud
  • Yandex Container Solution
    • Resource relationships
    • Graphics processing units (GPUs)
      • Overview
      • Disks
      • Disk snapshots
      • Creating scheduled snapshots
      • Non-replicated disk placement groups
      • File storages
      • Read and write operations
    • Images
    • Dedicated host
    • Reserved instance pools
    • Encryption
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • Spread placement
  • Partition placement
  • See also
  1. Concepts
  2. Disks and file storages
  3. Non-replicated disk placement groups

Non-replicated disk placement groups

Written by
Yandex Cloud
Updated at July 9, 2025
  • Spread placement
  • Partition placement
    • See also

When creating non-replicated disks, resources are automatically distributed across the Yandex Cloud physical infrastructure. Your disks might get hosted on the same physical media. To make multiple disk failures less likely, you can combine your disks into placement groups.

Grouping non-replicated disks reduces the risk of their simultaneous failure. However, the placement requirements are more demanding, so a physical resource shortage is more likely for non-replicated disks in a placement group rather than for the same number of ungrouped disks. You might fail to create a non-replicated disk in a placement group, but succeed to create one outside the group without any issue.

You can only place a non-replicated disk in a single group, which must reside in the same availability zone.

For more information about the organizational and technical limits of placement groups, see Quotas and limits in Compute Cloud.

In a placement group, non-replicated disks are located in the server racks of the data center of the selected availability zone according to one of the placement strategies.

Spread placementSpread placement

Spread placement is a non-replicated disk placement strategy which ensures that each disk resides on a separate server rack in the data center of the selected availability zone. If one of the server racks hosting the group's disks fails, only one disk will be affected.

Partition placementPartition placement

Partition placement is a non-replicated disk placement strategy where partitions with disks are guaranteed to reside on different server racks in a data center of the selected availability zone. If one of the server racks with the group's partitions fails, only one partition will be affected. A single partition may host multiple disks. A single placement group may contain up to 5 partitions.

See alsoSee also

  • How to create a disk placement group.
  • How to create a non-replicated disk in a placement group.
  • How to add a disk to a placement group.

Was the article helpful?

Previous
Creating scheduled snapshots
Next
File storages
© 2025 Direct Cursus Technology L.L.C.