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

XMLWordPrintableJSON

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

      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
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: