Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38441

In-Memory pins all dirty data in cache because of read concern majority

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • 3.6.9, 4.0.4
    • None
    • Replication, Storage
    • None
    • ALL
    • 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.
    • Repl 2019-01-14

    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:

      Attachments

        Issue Links

          Activity

            People

              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: