[SERVER-21308] fsm-suite doesn't wait long enough for the distributed lock when dropping a collection Created: 05/Nov/15 Updated: 17/Nov/15 Resolved: 06/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| 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. |
| Comments |
| Comment by Githook User [ 06/Nov/15 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |