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

NamespaceSerializer lock should be used for database as well as collection during createCollection

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.1, 4.1.1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Sharding 2018-07-16
    • 17

    Description

      In ConfigSvrCreateCollectionCommand here here we use the NamespaceSerializer for the collection lock, but not the database lock. Since we also need to take the distlock for the database, we should also use the NamespaceSerializer for that too. Otherwise we end up with timeouts in situations with high concurrency.

      Attachments

        Issue Links

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              matthew.saltz@mongodb.com Matthew Saltz
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: