[SERVER-22852] Fatal assertion 17508 after receiving CTRL_SHUTDOWN_EVENT on Windows Created: 25/Feb/16 Updated: 05/Feb/18 Resolved: 05/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 3.2.0-rc4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Robert Guo (Inactive) | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | platforms-needs-37-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | This was observed once and no repro has been found so far. |
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The server may fassert when seeing a null GlobalServiceContext after getting a CTRL_SHUTDOWN_EVENT logs:
code:
|
| Comments |
| Comment by Mark Benvenuto [ 26/Feb/16 ] |
|
CTRL_SHUTDOWN_EVENT is triggered by rebooting or shutting down the machine. MongoDB will receive this signal when it is not run as an NT service. When MongoDB is run as a service, we get SERVICE_CONTROL_PRESHUTDOWN sent to MongoDB first. You are right that CTRL+C should have the same effect in this case as CTRL_SHUTDOWN_EVENT. The source of the bug is probably some sort of race that occurred during termination or GlobalServiceContext was not set. |