[SERVER-38441] In-Memory pins all dirty data in cache because of read concern majority - MongoDB Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Works as Designed
Affects Version/s: 3.6.9, 4.0.4
Fix Version/s: None
Component/s: Replication, Storage
Labels:
None

Operating System:
ALL
Steps To Reproduce:

Hide

1. Launch a replica set using the In-Memory storage engine without explicitly disabling read concern majority.
2. Perform a significant amount of inserts.
3. View that dirty pages are not evicted.

Show
1. Launch a replica set using the In-Memory storage engine without explicitly disabling read concern majority. 2. Perform a significant amount of inserts. 3. View that dirty pages are not evicted.
Sprint:
Repl 2019-01-14
Case:

Description

By default, the In-Memory storage engine runs into read concern majority cache problems. If read concern majority is not explicitly disabled at startup, all dirty data remains pinned in cache because In-Memory never commits the data as the normal WiredTiger engine does.

Default settings:

--enableMajorityReadConcern false: