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
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Processing
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
      • Connecting to a cluster
      • Updating a cluster
      • Migrating a lightweight cluster to a different availability zone
      • Deleting a cluster
    • Setting up and using Python virtual environments
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • FAQ
  1. Step-by-step guides
  2. Yandex Data Processing clusters
  3. Migrating a lightweight cluster to a different availability zone

Migrating a lightweight Yandex Data Processing cluster to a different availability zone

Written by
Yandex Cloud
Updated at January 23, 2025

Subclusters of each Yandex Data Processing cluster reside in the same cloud network and availability zone. You can migrate a cluster to a different availability zone. The migration process depends on the cluster type:

  • The following describes how to migrate lightweight clusters.
  • For more information about migrating HDFS clusters, see this guide.

To migrate a lightweight cluster to a different availability zone:

  1. Make sure security groups are configured in your network.
  2. Create a subnet in the availability zone you are migrating you cluster to.
  3. Set up a NAT gateway and link a route table to the new subnet.
  4. Create a cluster in the appropriate availability zone.
  5. Delete the cluster in the source availability zone.

Note

The Intel Broadwell platform is not available for clusters with hosts residing in the ru-central1-d availability zone.

Was the article helpful?

Previous
Updating a cluster
Next
Deleting a cluster
© 2025 Direct Cursus Technology L.L.C.