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

Separate oplog from regular collections

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution

      The amount of if (oplog) special handling is increasing. Collection copy-on-write is disabled for the oplog for example. When the oplog pretends to be just another collection it makes it difficult to understand its semantics.

      We should consider separating the oplog from regular collections. Let the oplog have its separate API when necessary to clarify the semantics and avoid conditionals in the implementation.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: