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

Concurrent step downs due to step down via heartbeat and force reconfig should ensure that the term maintained by topology coordinator is set to TopologyCoordinator::_pendingTermUpdateDuringStepDown.

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • v4.0, v3.6

    Description

      Force reconfig cmd and force reconfig via heartbeat should be able to take care of updating the term & resetting _pendingTermUpdateDuringStepDown (like we do it in unconditional step down) if they cause step down and _pendingTermUpdateDuringStepDown is set.

      This is a 4.0 bug and the fix must be backported.

       

       Consequence of this bug is that this requires another heartbeat or metadata update (e.g.. during oplog fetching) to update the term again. (see SERVER-28290).

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: