# What is the replacement of the enableMajorityReadConcern = false option?

**URL:** <https://forums.percona.com/t/what-is-the-replacement-of-the-enablemajorityreadconcern-false-option/17848>\
**Category:** Percona Server for MongoDB\
**Created:** [October 5, 2022, 2:59am UTC](https://forums.percona.com/t/what-is-the-replacement-of-the-enablemajorityreadconcern-false-option/17848 "2022-10-05T02:59:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chadr](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/chadr/32/3923_2.png) [@chadr](https://forums.percona.com/u/chadr)\
**Post date:** [October 5, 2022, 2:59am UTC](https://forums.percona.com/t/what-is-the-replacement-of-the-enablemajorityreadconcern-false-option/17848/1 "2022-10-05T02:59:57Z")

</div>

Starting from the MongoDB 5.0, I cannot set enableMajorityReadConcern=false option as it was completely removed from MongoDB.

I’m deploying MongoDB cluster with PSA topology with in-memory storage engine but once the Secondary has been down and keep it to be down very long time, the oplog size of the Primary was increasing, eventually the Primary was also down due to ExceededMemoryLimit error without enableMajorityReadConcern=false option.

How to prevent the increasing of oplog size on Primary member in such situation starting from MongoDB 5.0?

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [October 5, 2022, 11:34am UTC](https://forums.percona.com/t/what-is-the-replacement-of-the-enablemajorityreadconcern-false-option/17848/2 "2022-10-05T11:34:05Z")

</div>

Hi, first of all PSA topology is not recommended for prod usage. That being said you may use the procedure described at [https://www.mongodb.com/docs/manual/tutorial/mitigate-psa-performance-issues/#std-label-performance-issues-psa](https://www.mongodb.com/docs/manual/tutorial/mitigate-psa-performance-issues/#std-label-performance-issues-psa) to get past this issue.