[SERVER-24729] stagger the launching of resmoke jobs Created: 22/Jun/16 Updated: 21/Sep/16 Resolved: 20/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Isabella Siu (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | TIG 18 (08/05/16) | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
BF-2654 was a failure that I think was due to 16 jobs all starting at exactly the same time. The tests in that particular suite tend to all follow the same setup, so all jobs simultaneously put a huge load on the disk system as they all started. To avoid this issue, I think we should put a half-second (or full-second) delay between the launching of multiple jobs in resmoke. |
| Comments |
| Comment by Githook User [ 20/Jul/16 ] |
|
Author: {u'name': u'iwysiu', u'email': u'isabella.siu@10gen.com'}Message: |