[SERVER-5703] ntservice should not have to fake out exitCleanly() to achieve its ends Created: 25/Apr/12 Updated: 02/Nov/21 Resolved: 02/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows |
||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The implementation of shutting down mongod when it is installed as an ntservice requires some clever faking out of the exitCleanly/dbexit logic, allowing those functions to sometimes return (based on the supplied exit code). A future design should separate the logic of "do the cleanup required for shutdown" from "terminate the current process", so that the ntservice module can implement the last step separately from the route taken by exitCleanly(). |
| Comments |
| Comment by Mark Benvenuto [ 25/Oct/21 ] |
|
There is now a separate shutdown and shutdownNoTerminate (which the nt service code uses) code path. This ticket can be closed. |
| Comment by Geert Bosch [ 25/Oct/21 ] |
|
henrik.edin, mark.benvenuto, schwerin Do we still need to do something here, or can we just close this? |