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

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Judah Schvimer
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: