-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:None
-
Fully Compatible
-
ALL
-
0
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.