-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Replication
-
ALL
As per the docs, you must set writeConcernMajorityJournalDefault to false if you are running voting, but non-journaling, nodes in your replica set:
https://docs.mongodb.com/manual/reference/replica-configuration/#rsconf.writeConcernMajorityJournalDefault
If you do not do this, the effect will be that your majority writes may hang if a majority of nodes includes a non-journaling node.
A worse effect is that if you also use --enableMajorityReadConcern, the commit level will never advance, and so the majority snapshot never advances. This can eventually fill up cache memory with write history.
- related to
-
SERVER-29649 Add startupWarning when a replset node is running with --nojournal but hasn't set writeConcernMajorityJournalDefault to false
- Closed
-
SERVER-38685 Startup warning if In-Memory SE is used and writeConcernMajorityJournalDefault is true
- Closed