Details
-
New Feature
-
Resolution: Duplicate
-
Minor - P4
-
None
-
None
-
None
-
(copied to CRM)
Description
Currently, all caught signals (with the exception of SIGUSR1) result in the mongod process shutting down cleanly, but without considering replication status as done via the shutdown command. It would be helpful if one of the signals could indicate a desire to attempt the full shutdown process (even if it cannot complete due secondaries not being caught up).
Attachments
Issue Links
- duplicates
-
SERVER-38994 Step down on SIGTERM
-
- Closed
-