[SERVER-31886] Powercycle tasks running on Windows Created: 09/Nov/17 Updated: 30/Oct/23 Resolved: 21/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.3, 3.7.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Jonathan Abrahams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | TIG 2017-12-04 | ||||||||
| Participants: | |||||||||
| Description |
|
Add Powercycle tasks that run on Windows. |
| Comments |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams', 'username': 'hptabster'}Message: |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams', 'username': 'hptabster'}Message:
(cherry picked from commit dcaf6432b7219d57cc5cf0de56b61264b8155e5d) |
| Comment by Githook User [ 21/Nov/17 ] |
|
Author: {'name': 'Jonathan Abrahams', 'username': 'hptabster', 'email': 'jonathan@mongodb.com'}Message:
|
| Comment by Max Hirschhorn [ 15/Nov/17 ] |
|
jonathan.abrahams, resmoke.py effectively uses a server selection timeout of 5 minutes in order to accommodate slow mongod startup on our test machines. This had been found to be necessary for our OS X hosts rather our Windows hosts, but I'm curious if the pymongo.errors.ServerSelectionTimeoutError exceptions you're seeing go away if you decide to wait even longer. I had peeked at the mongod output and I saw the process eventually logs "waiting for connections on port 20001". (The reason we don't specify a timeout_millis of 5 minutes directly is because PyMongo won't return early from its server selection loop even if TCP says there's nothing on the other side. This behavior is undesirable for an interactive program because it meant hitting Ctrl+C at an inopportune moment would mean it would take resmoke.py 5 minutes to exit cleanly. It's probably sufficient for the purposes of the powertest.py script to set the server selection timeout this way for now.) Could you post a status update with any other issues you're still seeing so that we can try and brainstorm suitable workarounds for them? |