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

Allow stepDown command to work against primary in catchup mode

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.6, 3.5.7
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-05-08

    Description

      Stepdown command ensures a majority of caught up nodes. It does so by waiting for the _lastCommittedOpTime to reach the last applied optime. However, during catchup, the primary cannot advance its _lastCommittedOpTime until it commits an operation in its term. Thus stepdown command will fail due to timeout if the _lastCommittedOpTime isn't updated before the election. We could fix this by using the same logic that awaitReplication() uses for determining whether a majority of nodes are at the given time, rather than using _lastCommittedOpTime directly.

      Attachments

        Issue Links

          Activity

            People

              siyuan.zhou@mongodb.com Siyuan Zhou
              siyuan.zhou@mongodb.com Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: