[SERVER-17820] Windows service stop can lead to mongod abrupt termination due to long shutdown time Created: 31/Mar/15 Updated: 18/Sep/15 Resolved: 03/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.3, 3.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Completed: | |||||||||||||
| Participants: | |||||||||||||
| Description |
|
Issue Status as of Apr 29, 2015 ISSUE SUMMARY WORKAROUNDS AFFECTED VERSIONS FIX VERSION Original description
Recovery should succeed ( |
| Comments |
| Comment by Githook User [ 20/Apr/15 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |
| Comment by Githook User [ 20/Apr/15 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: (cherry picked from commit 7060c72b30a836b3052f7890ea8c4b592014adf4) |
| Comment by Githook User [ 03/Apr/15 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |
| Comment by Daniel Pasette (Inactive) [ 31/Mar/15 ] |
|
I'm adding to "3.1 Required" It can be quite common for the server to take a while to shutdown cleanly. |
| Comment by Mark Benvenuto [ 31/Mar/15 ] |
|
For normal service stop(SERVICE_CONTROL_STOP), I think it can wait an almost indefinite time as low as it continues to report progress correctly (ie, not hung). It can be almost indefinitely. For SERVICE_CONTROL_SHUTDOWN, it can wait a max of 5 seconds on my Windows 8.1 machine, and I think 12 seconds on Windows Server 2008 R2. https://msdn.microsoft.com/en-us/library/windows/desktop/ms685149%28v=vs.85%29.aspx We need to call exitCleanly on a separate thread in order to fix this. |