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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.1, 4.1.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Sharding 2018-07-16
    • 17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Janna Golden
            Reporter:
            Matthew Saltz (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: