Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication, Storage
Labels:
- neweng

Assigned Teams:

Replication
Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Eric Milkie
Participants:: [DO NOT USE] Backlog - Replication Team, Eric Milkie, Siyuan Zhou, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Sep 19 2017 05:29:58 PM UTC
Updated:: Dec 06 2022 03:51:44 AM UTC
Resolved:: Apr 09 2020 05:42:46 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates