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

Fix updating optimes from remote nodes

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • ALL
    • 0

    Description

      Currently, it is possible for a node to erroneously update its own lastAppliedOptime when all of these conditions are true:

      • the node is PRIMARY
      • the node was SECONDARY in the past and has chained through another secondary
      • the node does further writes before receiving a handshake from the chaining secondary

      In such a situation, we rewind our own optime in the slavemap, but do not update the legacy replset's lastappliedoptime, which causes an fassert failure.

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: