Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
4.0.4
-
Fully Compatible
-
v4.0, v3.6
-
Repl 2019-06-03, Repl 2019-06-17
Description
We should a startup warning if a node is using the In-Memory storage engine but has also enabled writeConcernMajorityJournalDefault. Per the documentation, that option is unsupported in replica sets that contain In-Memory nodes and can cause problems if not set to false.
Attachments
Issue Links
- is documented by
-
DOCS-12778 Docs for SERVER-38685: Startup warning if In-Memory SE is used and writeConcernMajorityJournalDefault is true
-
- Closed
-
- is related to
-
SERVER-35786 lastDurable optime should be updated after batch application on non-durable storage engines
-
- Backlog
-
-
SERVER-31158 voting inMemory nodes should refuse to join replica sets that have writeConcernMajorityJournalDefault set to true
-
- Closed
-
-
SERVER-38441 In-Memory pins all dirty data in cache because of read concern majority
-
- Closed
-