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

XMLWordPrintableJSON

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

      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:

        1. Screen Shot 2018-12-06 at 3.39.57 PM.png
          87 kB
          Danny Hatcher
        2. Screen Shot 2018-12-06 at 3.41.05 PM.png
          91 kB
          Danny Hatcher

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

              Created:
              Updated:
              Resolved: