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

Prevent test from dropping collections directly against a shard

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Sharding 2019-10-21, Sharding 2019-11-04
    • Linked BF Score:
      19

      Description

      Problem Statement

      Dropping a collection directly from a shard on a sharded cluster is not a supported action. If one drops a collection directly while a migration is happening for that collection, issues can arise. Such as the following:

      If a collection/db is dropped from the recipient shard after it finishes cloning from the donor shard, it's possible that the migration still commits. The config will still think the recipient shard owns the chunk from the migration, but the shard will not know about the collection at all.

      Fix

      Change the linked test to drop the collection against the mongos instead of the shard.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              blake.oler Blake Oler
              Reporter:
              janna.golden Janna Golden
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: