Allow more graceful shutdown from signals

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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).

              Assignee:
              Mira Carey
              Reporter:
              Chris Harris
              Votes:
              4 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: