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

Dropping sharded database or collection leaves orphaned zone documents

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.2.18, 3.4.10, 3.6.2, 3.7.1
    • None
    • Sharding

    Description

      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.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35441 drop/dropDatabase does not cleanup config.tags

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17397 Dropping a Database or Collection in a Sharded Cluster may not fully succeed

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: