Cleanup leftover collection metadata after drop

XMLWordPrintableJSON

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

      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:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            David Hows (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: