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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • 135
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: