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

Avoid G_X lock for rename_collection within database

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • 2.7.7
    • 3.4.10, 3.5.10
    • Concurrency, Storage
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Storage 2017-07-31

    Description

      Probelm:

      See https://github.com/mongodb/mongo/blob/master/src/mongo/db/commands/rename_collection.cpp#L113

                  Lock::GlobalWrite globalWriteLock(txn->lockState());

      Solution:
      Scope this lock as a DB_X when renaming within a database. Renaming between databases probably still requires a G_X or perhaps two DB_X locks.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30037 Fix replset timeouts with collectionUUIDs enabled

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30087 convertToCapped should not yield locks before renaming

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-10528 Docs for SERVER-15723: Avoid G_X lock for rename_collection within database

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

          Bug - A problem which impairs or prevents the functions of the product. DOCS-10992 convertToCapped is missing the 'global write lock' warning

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

          Activity

            People

              geert.bosch@mongodb.com Geert Bosch
              alvin Alvin Richards (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: