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

NamespaceSerializer lock should be used for dropCollection

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.2, 4.1.2
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Sharding 2018-08-13
    • 17

    Description

      NamespaceSerializer was added to createCollection to prevent unneeded timeouts occurring when several create operations in parallel try to acquire the same distributed lock. The same should be applied to dropCollection.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31643 Make drop collection in concurrency workloads retry LockBusy errors

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36433 NamespaceSerializer lock should be used during drop database

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-47422 Use NamespaceSerializer when taking distributed locks for refineCollectionShardKey and migrations

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-49145 Prevent distributed lock timeouts in suites with background migrations

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

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              matthew.saltz@mongodb.com Matthew Saltz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: