Dropping sharded database or collection leaves orphaned zone documents

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.2.18, 3.4.10, 3.6.2, 3.7.1
    • Component/s: Sharding
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a database or collection is dropped in a sharded cluster, the drop code leaves around any zones which might have been defined. This is not only problematic because it leaves orphaned data around, but also because if the same collection is later recreated, the old zones will take effect possibly unknown to the user.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Kaloian Manassiev
            Votes:
            3 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: