[SERVER-18599] resmoke.py should wait longer for mongod to start Created: 21/May/15 Updated: 19/Sep/15 Resolved: 21/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.1.3 |
| Fix Version/s: | 3.1.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Quint Iteration 4 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Waiting up to 30 seconds for a connection to be established to a newly-started mongod process is insufficient on some build variants in Evergreen. This is likely due to file preallocation, disk speed, and other resource factors. Increasing the timeout to 5 minutes should provide more than enough time for any initialization to occur, regardless of the hardware of the Evergreen host machines. |
| Comments |
| Comment by Githook User [ 21/May/15 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: Change resmoke.py to wait up to 5 minutes for a mongod/mongos process |