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

persist Rollback ID and read it at startup

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.7
    • Replication
    • None
    • Fully Compatible
    • Repl 2017-05-08
    • 0

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-28988 add ReplicationProcess and use it to cache Rollback ID

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-45178 Rollback via refetch can cause rollback to happen successfully w/o updating the rollback id.

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-32776 Refresh rollback id cache on increment

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: