liveBook · Manning

Atlas Search Node

As explained in MongoDB 8.0 in Action, Third Edition

An Atlas Search Node is a specialized MongoDB Atlas node that runs search services separately from database-serving processes.

An Atlas Search Node is a specialized MongoDB Atlas node that runs the mongot search process separately from database-serving processes. This separation isolates search workloads from other database operations. section 11.3.2

Atlas automatically assigns a mongod to each mongot. The mongot process synchronizes search indexes with its mongod through initial synchronization and ongoing change-stream updates. section 11.3.2 section 11.8

Use dedicated search nodes when:

  • You need search operations isolated from database-serving workloads. section 11.3.2
  • You run a dedicated M10-or-higher sharded or unsharded Atlas cluster. section 11.3.2
  • You need greater search performance for large vector-search datasets and can accept higher resource consumption. section 12.6

Sizing across shards

Deploying two Search Nodes for a three-shard cluster produces six Search Nodes: two dedicated to each shard. Reserve an additional 20% local SSD capacity for search-index operations. section 11.3.2

Figure 11.4 Within the Atlas Search Nodes architecture, multiple MongoDB (mongod) instances manage data storage and execute search queries, forwarding them to mongot processes. These processes handle initial synchronization and continuous updates via change streams, ensuring that search indexes are consistently updated with the latest data changes across all nodes. (Image © MongoDB 2024 CC BY-NC-SA 3.0)
A diagram of a computer network

Description automatically generated

The architecture diagram traces data-serving mongod instances, search-serving mongot processes, initial synchronization, and continuous index updates. section 11.3.2

How MongoDB 8.0 in Action, Third Edition covers it

How deep it goes
Explains deployment scope, process separation, synchronization, shard allocation, and storage overhead.
Examples
Uses a three-shard, two-nodes-per-shard deployment and a 20% local-SSD storage-overhead requirement.
What it assumes
Assumes MongoDB Atlas deployment knowledge and a dedicated M10-or-higher sharded or unsharded cluster.
What you can do after
Operate/configure dedicated search capacity for eligible Atlas clusters and assess its performance and resource trade-offs.
How it connects
Connects mongot, mongod, change streams, Apache Lucene, Atlas Search, and Atlas Vector Search.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of MongoDB 8.0 in Action, Third Edition. The section links point to the parts of the book it draws on.