Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Compute Cloud
  • Yandex Container Solution
    • Resource relationships
      • Overview
      • Platforms
      • vCPU performance levels
      • Preemptible VMs
      • VM network interfaces
      • Software-accelerated network
      • Live migration
      • Placement groups
      • Statuses
      • VM maintenance policies
      • Resetting Windows VM passwords
    • Graphics processing units (GPUs)
    • Images
    • Dedicated host
    • Encryption
    • Backups
    • Quotas and limits
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes

In this article:

  • Spread placement
  • Partition placement
  • See also
  1. Concepts
  2. Virtual machines
  3. Placement groups

VM placement groups

Written by
Yandex Cloud
Updated at April 26, 2024
  • Spread placement
  • Partition placement
  • See also

Once VMs are created, they are automatically distributed across the Yandex Cloud physical infrastructure. To manage hardware fault tolerance levels, you can combine your VMs into placement groups.

VM placement groups are groups of VMs, where each one is hosted on physical hardware according to a certain strategy. Yandex Compute Cloud uses the spread placement and partition placement strategies.

To learn about the limits on the number of VM placement groups, see Quotas.

Spread placementSpread placement

Spread placement is a VM placement strategy ensuring that each instance is hosted on a separate server rack in one of the availability zones. If one rack fails, the others continue to run normally.

By grouping VMs based on the spread placement strategy, you can ensure a high level of fault tolerance and reduce the risk of concurrent failure of VMs hosted on the same server rack. However, the placement requirements are more demanding, so a physical resource shortage is more likely for VMs in a placement group rather than for the same number of ungrouped VMs.

To learn about the limits on the number of VMs per group with the spread placement strategy, see VM limits.

You can manage VM placement groups that follow the spread placement strategy using the management console, CLI, Terraform, or API.

Partition placementPartition placement

Partition placement is a VM placement strategy that ensures that VMs from different partitions reside on different server racks in the data center of one of the availability zones. If one of the server racks hosting the group partitions fails, only one partition will be affected.

A single placement group may contain up to 5 partitions. To learn about the limits on the number of VMs per partition, see Quotas.

You can manage placement groups that follow the partition placement strategy using the CLI and API.

See alsoSee also

  • How to create a placement group
  • How to add a VM instance to a placement group
  • How to create a VM in a placement group

Was the article helpful?

Previous
Live migration
Next
Statuses
Yandex project
© 2025 Yandex.Cloud LLC