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

Investigate removing use of the DatabaseHolder and/or dropDatabase oplog entry in the storage execution layer

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Storage Execution
    • 135

      The server supports many database level commands, but in the storage execution layer those mostly devolve to scanning the CollectionCatalog. Keeping the DatabaseHolder in-memory state in sync with the CollectionCatalog is buggy. Today dropDatabase majority commits dropCollection oplog entries, then as a second step writes the dropDatabase oplog entry and clears the in-memory state.

      Perhaps we don't need to write dropDatabase anymore. Sharding does a bunch of writes to clear database level state in its own config, regardless of the dropDatabase oplog entry.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: