[SERVER-5073] replsetrestart1.js fails in 32-bit Windows Created: 24/Feb/12 Updated: 11/Jul/16 Resolved: 24/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | Windows, buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
32-bit Windows |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
The replsetrestart1.js test fails in 32-bit Windows because a "shutdown" command without force does not shut down the primary within the 30 seconds we wait before forcefully terminating the process. When we terminate the process, this leaves the mongod.lock file in place and in 32-bit we don't have journaling by default, so the restart of the primary fails. Adding a force option to the shutdown command sent by the shell makes the shutdown happen, and raising the timeout from 30 seconds to 60 seconds reduces the window for a race. In the logs of the failure, the primary is still trying to talk to the (no longer running) secondaries right up until it gets terminated. |
| Comments |
| Comment by auto [ 24/Feb/12 ] |
|
Author: {u'login': u'tadmarshall', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: Use the "force" option in the Windows version's kill_wrapper() |