Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 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
    • High availability clusters
    • Sharding
    • Host types
    • Users and roles
    • Maintenance
    • Supported clients
    • Yandex StoreDoc settings
    • Yandex StoreDoc versioning policy
  • Access management
  • Inspections and recommendations
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Replication

Replication in Yandex StoreDoc

Written by
Yandex Cloud
Updated at September 14, 2026
View in Markdown

Replication in a Yandex StoreDoc cluster is enabled when there are two or more non-hidden hosts. Each replica host stores a copy of the same dataset.

Types of replicas in a Yandex StoreDoc cluster:

  • Primary replica (master): Automatically selected from among non-hidden hosts and accepts all write requests.
  • Secondary replicas: Asynchronously copy all changes from the primary replica.

Read requests can be processed both on secondary replicas and the primary replica, depending on the readPreference connection parameter.

Primary replica failoverPrimary replica failover

If the primary replica fails or is switched over manually, Yandex StoreDoc will automatically select a new primary replica from among the non-hidden hosts.

You can influence the primary replica selection in a Yandex StoreDoc cluster by configuring priorities for cluster hosts. The highest priority host will become the new primary replica.

You can set the host priority using the YC CLI, API, or Terraform:

  • When creating a cluster or a host in a cluster.
  • When changing the host settings.

The default priority value of 1 represents the lowest priority. The minimum value is 0. A host with this priority level cannot become the primary replica, even for absence of other suitable hosts in the cluster. The maximum value is 1000. Only integer values can be used.

Was the article helpful?

Previous
Backups
Next
High availability clusters
© 2026 Direct Cursus Technology L.L.C.