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

persist Rollback ID and read it at startup

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.7
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-05-08
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we randomize rollback IDs at startup to reduce the chance of collisions. This does not prevent collisions entirely and makes it so rollback IDs that are randomly chosen very close to MaxInt could rollover into the negatives which is somewhat undefined behavior. We should simply persist the rollback ID (waiting for it to be durable) and read it at startup like lastVote to avoid these issues.

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: