Prev Next

Database / Milvus Vector database Interview questions

What is a Replica in Milvus?

A Replica is an additional, independently loaded copy of a collection's segments onto a separate set of Query Nodes, used to increase both search throughput (more replicas can serve concurrent queries in parallel) and fault tolerance (if one replica's Query Nodes go down, another replica can continue serving search requests).

client.load_collection(collection_name="products", replica_number=2)

Replicas are specifically a read-scaling and availability mechanism, distinct from how Milvus handles write durability (which relies on the write-ahead log and object storage). Adding replicas increases the memory and compute cost of loading a collection proportionally, since each replica genuinely duplicates the loaded segment data onto its own set of Query Nodes rather than sharing the underlying loaded copy.

Replicas in Milvus primarily improve:
Adding more replicas to a loaded collection:

More Related questions...

What is Milvus? What is a vector database, and how does Milvus fit that category? What is a Collection in Milvus? What is a Partition in Milvus? What is a Segment in Milvus? What is an embedding vector, in the context of Milvus? What is an index in Milvus, and why is it needed? What are the main vector index types Milvus supports? What is HNSW, and why is it commonly used in Milvus? What are the similarity/distance metrics Milvus supports? What is the difference between L2 and Cosine similarity in Milvus? What is Milvus Lite? What is Zilliz Cloud? What are the main components of Milvus's architecture? What is the Proxy component in Milvus? What is a Query Node in Milvus? What is a Data Node in Milvus? What is loading a collection in Milvus, and why is it required before search? What is a scalar field in Milvus, and how is it used with vector search? What is dynamic schema in Milvus? What are Milvus's consistency levels? What is a Replica in Milvus? What is hybrid search in Milvus? What is a sparse vector in Milvus? What are the main use cases for Milvus? Explain the data flow of an insert operation in Milvus, from client to searchable segment? Why does Milvus separate compute and storage in its architecture? How does Milvus differ from a traditional relational database for storing vector data? What is the difference between IVF_FLAT and HNSW indexes in Milvus? How do you choose the right index type for a given Milvus workload? When should you use IVF_PQ instead of IVF_FLAT? How do you troubleshoot slow search performance in Milvus? What is the difference between growing segments and sealed segments in Milvus? How does Milvus handle search on data that hasn't been indexed yet? Explain the internal working of Milvus's segment sealing and index-building pipeline? What is the difference between Milvus and Pinecone? How do you implement multi-tenancy in Milvus? Why use Partitions instead of separate Collections for data isolation? What is the difference between Strong and Bounded Staleness consistency in Milvus? How does Milvus's Timestamp Oracle (TSO) ensure operation ordering? When would you choose GPU-accelerated indexes (like CAGRA) over CPU-based indexes? How do you configure replicas in Milvus for read scalability? What is the difference between the Coordinator services and Worker nodes in Milvus's architecture? Explain the lifecycle of a search request in a distributed Milvus cluster? How do you optimize Milvus for cost at billion-vector scale? What is the difference between Milvus's tiered storage and traditional single-tier storage? How does Milvus's hybrid search combine dense and sparse vector results? Why should you avoid over-partitioning a Milvus collection? What is the difference between Milvus 2.x's coordinator-based architecture and the direction of Milvus 3.0's lake-native design? How do you troubleshoot out-of-memory errors when loading a large Milvus collection?
Show more question and Answers...


Comments & Discussions