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

Cleanup leftover collection metadata after drop

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding

      Currently we do very limited cleanup of the config metadata following the drop of a database.

      We should add processes to cleanup old config entries, specifically:

      1. config.collections
      2. config.locks

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            david.hows David Hows
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: