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

arbiter should use commit level for its optime in elections

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.1.9
    • None
    • Replication
    • None
    • Fully Compatible
    • RPL 8 08/31/15, RPL A (10/09/15)
    • 0

    Description

      Since arbiters do not sync data, they should use the commit level when responding to requestVote commands.
      This means that they should respond 'nay' to a requestVote when the candidate's optime is behind the commit level. For non-arbiters, the usual logic is to respond 'nay' if the candidate's optime is behind the last op committed on the non-arbiter.
      As part of this work, we need to ensure that an arbiter's heartbeats are properly updating its commit level.

      Attachments

        Activity

          People

            scotthernandez Scott Hernandez (Inactive)
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: