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

Ensure upstream node doesn't roll back after checking minvald

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 3.2.12, 3.4.2, 3.5.2
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4, v3.2
    • Repl 2016-11-21, Repl 2016-12-12, Repl 2017-01-23, Repl 2017-02-13

    Description

      This is an extension of SERVER-25145. With that done, there is a gap between when we check the minvalid and when we are able to detect rollbacks. That means that our sync source could roll back to before our minvalid invalidating our prior check. This ticket is about closing that gap.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27403 Consider term and rbid when validating the proposed sync source

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25145 During rollback (or w/minvalid invalid) select sync source based on end OpTime

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

          Activity

            People

              mathias@mongodb.com Mathias Stearn
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: