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

Instead of looking at 'local.oplog.' collections in the WiredTiger integration code only look for the single collection 'local.oplog.rs'

    • Type: Icon: Improvement Improvement
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Execution Team 2021-01-25

      I suspect a lot can be cleaned up around this. E.g. there's a Namespace::oplog function, and WiredTigerKVEngine has a special counter _oplogManagerCounter to work around there being several local.oplog collections in order to start and stop the WiredTigerOplogManager once instead of several.

            Assignee:
            dan.larkin-york@mongodb.com Dan Larkin-York
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: