[SERVER-18202] Rewrite all distributed lock clock skew jstests as unit tests Created: 24/Apr/15 Updated: 13/Jul/15 Resolved: 13/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Sharding 8 08/28/15 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The existing jstests that use the _testDistLockWithSkew command are all fundamentally racy and fail periodically when the test machine runs unexpectedly slowly. |
| Comments |
| Comment by Andy Schwerin [ 13/Jul/15 ] |
|
Legacy distributed lock manager is going away after 3.2 is released, and hopefully so is the new distributed lock manager. |