Community Day Trivia #11: What is the minimum number of members in a replica set?

We’ll be posting trivia challenges throughout the Community Day event!

The best answer for each challenge will be marked as a solution and earn the poster a promo code for $100 of Atlas credits and a Community Day 2021 Trivia Winner forum badge that can also be used as a title on the forums.

A great answer will include some information such as a link to more information or a tip on how you figured out the solution.

You can help us decide the best answer to a trivia challenge by liking great responses! To give everyone a chance at earning Atlas credits, we will use “have you already had a trivia solution accepted” to break ties in favour of those who haven’t had a solution yet.

What is the minimum number of members in a replica set?

Hello Stennie,
you can convert a standalone server to a replica set. That way you have 1 member in a RS.

1 Like

From a production standpoint the minimum odd number would be three data-bearing nodes on three separate hosts preferably in separate availability zones, at the least, to maintain quorum.

But, technically just one like Michael mentioned.



Hi @mahisatya
for later readers: I completely agree with @mahisatya, never run a converted stand-alone server as RS in production. Ok you gain the chance to have an oplog but I would not sleep well with a 1 on node RS.

1 Like

Hi Folks,

As @Michael pointed out, 1 is the minimum number of members in a replica set and as @mahisatya mentioned 3 data-bearing members is the minimum number recommended for a production replica set.

Can anyone think of good use cases for a single member replica set?


While writing, testing and POC-ing transaction related code on local/dev/testing instances.


1 Like

You want to migrate a single instance to MongoDB Atlas.
Since a live migration requires a replicaset resp. an oplog you convert the single instance to a RS, activate the oplog and use mongomirror (Atlas live migration) to migrate the data to Atlas…

I would not claim it a day to day use case, but the simplest paths to migrate a single instance - so somehow this cold be the use case.


Good use cases for a 1 node replica set:

-Testing out change streams without needing a full replica set
-Point-In-Time Backup Requirement for a non-prod instance
-Proof of Concept that will eventually be expanded to a full replica set with 3+ members


Adding to @Michael_Grayson’s first point (Testing out change streams without needing a full replica set), testing out Transactions. I recently had a use case and found it useful and I had used the handy mtools for creating my RS.

1 Like