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

Initial sync should set the minValid document to the "stopTimestamp"

    • Fully Compatible
    • ALL
    • v6.1
    • 25

      Apologies for the prescriptive solution. matthew.russotto@mongodb.com agreed in thinking this would be the most straight-forward change.

      Here's an example of a minvalid check that can happen during initial sync which evaluates the wrong result.

      This was found via an unrelated test failure.

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: