Comments on: MongoDB – Converting Replica Set to Standalone https://www.percona.com/blog/mongodb-converting-replica-set-to-standalone/ Fri, 29 Dec 2023 00:26:49 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Sergei K https://www.percona.com/blog/mongodb-converting-replica-set-to-standalone/#comment-10973636 Fri, 03 Jun 2022 08:59:06 +0000 https://www.percona.com/blog/?p=79410#comment-10973636 In my practice, I have come across the fact that, in replica mode, Mongo works slower if there are active records or document changes (for example, aggregation with output to a new collection), because in addition to the records themselves, Mongo also writes a oplog. Therefore, it works faster in standalone mode, because it does not write a oplog.

]]> By: Richard Bateman https://www.percona.com/blog/mongodb-converting-replica-set-to-standalone/#comment-10973481 Thu, 06 Jan 2022 16:49:59 +0000 https://www.percona.com/blog/?p=79410#comment-10973481 Another simpler option is just to remove the extra members and leave it as a single-member replicaset — that may seem silly at first glance, but it leaves you flexibility for some things which you otherwise couldn’t do:

* Change Streams
* Add a hidden secondary to have a “hot backup”
* Be able to quickly and easily scale back up later if you need to

Personally it baffles me why anyone would run standalone in a production environment — there is basically no cost to having a single-member system and it leaves you options.

]]>