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

Enabling profiling and read concern majority with a workload of reads and no writes causes accumulation of dirty data

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.15, 3.4.6, 3.5.5
    • Component/s: Write Ops
    • None
    • Query
    • ALL

      Start a replica set with these options:

      mongod --enableMajorityReadConcern --profile 2 --wiredTigerCacheSizeGB 2 ...

      Then start a workload of reads but no writes:

          db.c.insert({})
    for (var i = 0; ; i++) {
        if (i%1000 == 0)
            print(i)
        db.c.findOne()
    }

      Range of pinned ids and dirty data grows, and instance hangs when dirty data in cache reaches 20%:

        1. better34.png
          143 kB
          Bruce Lucas
        2. repro.png
          119 kB
          Bruce Lucas

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: