Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Works as Designed
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.6.9, 4.0.4
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:
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

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: