Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.15, 4.2.0-rc0, 4.0.13
Affects Version/s: 4.0.4
Component/s: Replication
Labels:
- former-quick-wins
- neweng

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.0, v3.6
Sprint:
Repl 2019-06-03, Repl 2019-06-17
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

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.

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

Assignee:: Vishnu Kaushik
Reporter:: Danny Hatcher (Inactive)
Participants:: Danny Hatcher, Eric Milkie, Githook User, Tess Avitabile, Vishnu Kaushik
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Dec 18 2018 03:20:57 PM UTC
Updated:: Oct 29 2023 10:25:37 PM UTC
Resolved:: Jun 04 2019 06:16:15 PM UTC
Confidence Status Last Update:: 30/May/19 9:01 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates