Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38994

Step down on SIGTERM

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.8, 4.1.10
    • Component/s: Replication
    • Labels:
      None

      Description

      Kubernetes uses SIGTERM to spin down containers, and our sysv init and systemd unit files use SIGTERM to shutdown the mongodb service. It would greatly reduce election time and prevent potential data loss due to replicaset rollback if we were able to use the election handoff path of stepdown instead of waiting for the full electionTimeoutMillis.

        Attachments

          Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-40252 Signaling 1-node replica set to shut down now takes an extra 10 seconds

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-12561 Docs for SERVER-38994: Step down on SIGTERM

          • Major - P3 - Major loss of function.
          • Open
          related to

          Task - A task that needs to be done. SERVER-39424 Test that DDL operations can't succeed after prepared transactions are aborted during shutdown

          • Major - P3 - Major loss of function.
          • In Progress

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: