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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.1, 4.1.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Sharding 2018-07-16
    • Linked BF Score:
      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

              Assignee:
              janna.golden Janna Golden
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: