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

Config term and oplog entry can be out of date upon restart

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      During startup, we use the on-disk config and install that as our config. We then look at the top of the oplog and use that oplog entry's term as our term. It seems possible for this to be out of date, as we could have received a newer config via heartbeats and installed it, before we receive an oplog entry on this new term. This can lead to issues later if we try to run for election.

      Notably, this is only an issue if the newer term cannot be received post-startup via heartbeats. Otherwise, we would update our term via those heartbeats, and the config and term would be in sync again.

            Assignee:
            Unassigned Unassigned
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: