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
    • 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
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Roles and functions of different host types
  • Cluster composition depending on sharding type
  1. Concepts
  2. Host types

Host types in Yandex StoreDoc

Written by
Yandex Cloud
Updated at December 22, 2025
View in Markdown
  • Roles and functions of different host types
  • Cluster composition depending on sharding type

Yandex StoreDoc has these four host types: MONGOD, MONGOINFRA, MONGOCFG, and MONGOS. Each host type has a role and functions of its own in the cluster. The type and number of hosts in a Yandex StoreDoc cluster depend on what sharding type you select.

Roles and functions of different host typesRoles and functions of different host types

  • MONGOD: Data storage and query processing hosts. These hosts are present in both sharded and non-sharded clusters.

    Primary functions of MONGOD hosts:

    • Read and write request processing.
    • User data storage.
    • Data replication.
    • Ensuring data consistency.
  • MONGOCFG: Sharding configuration hosts. These hosts are present only in clusters with advanced sharding.

    Primary functions of MONGOCFG hosts:

    • Storing and updating sharding metadata on changes in the shard configuration.
    • Providing MONGOS hosts with up-to-date information about chunks and shards.
    • Coordinating chunk migration between shards.
  • MONGOS: Router hosts. These hosts are present only in clusters with advanced sharding.

    Primary functions of MONGOS hosts:

    • Accepting client connections.
    • Routing queries to shards.
    • Processing of query or subquery results.
    • Delivery of final output to the client.
  • MONGOINFRA: Infrastructure hosts. This host type combines the MONGOS and MONGOCFG roles. MONGOINFRA hosts are present only in clusters with standard sharding.

    Primary functions of MONGOINFRA hosts:

    • Accepting client connections.
    • Routing queries to shards.
    • Storing and updating sharding metadata on changes in the shard configuration.
    • Coordinating chunk migration between shards.
    • Processing of query or subquery results.
    • Delivery of final output to the client.

Cluster composition depending on sharding typeCluster composition depending on sharding type

The number of hosts of various types in an Yandex StoreDoc cluster depends on sharding type:

Sharding type MONGOD MONGOINFRA MONGOS MONGOCFG
No sharding ⩾ 1 — — —
Standard ⩾ 1 ⩾ 3 — —
Advanced ⩾ 1 — ⩾ 2 ⩾ 3

A non-sharded cluster consists exclusively of MONGOD hosts that process all client requests. Query routing is managed by the Yandex StoreDoc client.

A standard-sharded cluster consists of MONGOD and MONGOINFRA hosts.
Client requests addressed to the cluster are processed as follows:

  1. The Yandex StoreDoc client connects to all MONGOINFRA hosts and sends the request to one of them.
  2. The MONGOINFRA host analyzes the request and figures out what shards are affected by it.
  3. The MONGOINFRA host forwards the request or the group of subrequests to relevant MONGOD hosts.
  4. MONGOD hosts execute the request or subrequests.
  5. The MONGOINFRA host processes the result of the request or subrequests and returns the final result to the client.

A cluster with advanced sharding consists of MONGOD, MONGOS, and MONGOCFG hosts.
Client requests addressed to the cluster are processed as follows:

  1. The Yandex StoreDoc client connects to all MONGOS hosts and sends the request to one of them.
  2. The MONGOS host analyzes the request and uses metadata from MONGOCFG hosts to figure out what shards are affected by it.
  3. The MONGOS host forwards the request or the group of subrequests to relevant MONGOD hosts.
  4. MONGOD hosts execute the request or subrequests.
  5. The MONGOS host processes the result of the request or subrequests and returns the final result to the client.

Was the article helpful?

Previous
Sharding
Next
Users and roles
© 2026 Direct Cursus Technology L.L.C.