-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.1.11
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Service Arch 2019-05-20
The NonAuthTaskExecutor thread is created as part of the ServiceContext creation, through the ConstructorActionRegisterer.
We construct the service context here. However, we don't set up the signal masks or the signal processing thread until later (here).
This means that the NonAuthTaskExecutor thread will not have the "async" signals masked off. This can prevent a clean shutdown when the server gets a SIGTERM, as the NonAuthTaskExecutor thread may be chosen to handle it instead of the signal processing thread.
I think the best way to fix this would be to move the creation of NonAuthTaskExecutor to after the signal processing thread is created.
- is depended on by
-
SERVER-39447 $mongotRemote Implementation Work
- Closed