Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12561

Docs for SERVER-38994: Step down on SIGTERM

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.10, 4.0.8, 3.6.15
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Description:

      This changes the behavior of clean shutdown.

      Probably most noticeable for users, a shutdown initiated by SIGTERM will now attempt a step down in a way very similar to the shutdown command without arguments. It differs in that:

      • Where a default shutdown command would have failed, returning to the user with an error, failing to stepdown will not stop shutdown in this path.
      • The node will not vote in elections that occur after the step down

      Engineering Ticket 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.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              kay.kim Kay Kim (Inactive)
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 41 weeks, 2 days ago
                Date of 1st Reply: