[SERVER-20702] Sleep test command should optionally not take a lock Created: 30/Sep/15 Updated: 28/Sep/16 Resolved: 09/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: | Samantha Ritter (Inactive) | Assignee: | Samantha Ritter (Inactive) |
| 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 | ||||||||||||||||
| Sprint: | Platform C (11/20/15) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The sleep test command would be more useful if it could optionally run without taking a global read or write lock. For certain tests, it isn't necessary to block other operations on the database while a sleep command waits. For example, when using this command solely as a way to have a db operation take a specified amount of time, we do not care if other operations are permitted to run concurrently. |
| Comments |
| Comment by Githook User [ 09/Nov/15 ] |
|
Author: {u'username': u'samantharitter', u'name': u'samantharitter', u'email': u'samantha.ritter@10gen.com'}Message: |