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

fsm-suite doesn't wait long enough for the distributed lock when dropping a collection

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0-rc3
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      0

      Description

      The FSM suite occasionally gets "Error: drop failed: Lock for drop is taken" when it tries to drop a collection. We already wait 10 minutes at cleanup to get the distributed lock, but we only wait the default 2 seconds everywhere else. We're getting the error occasionally at setup, but also could during any workload that drops a collection. This error began to arise more often after we turned the balancer back on because there is now more contention for the lock.

        Attachments

          Activity

            People

            Assignee:
            judah.schvimer Judah Schvimer
            Reporter:
            judah.schvimer Judah Schvimer
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: