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

Backup cursor truncate after test can choose to recover before the checkpoint timestamp

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.6
    • None
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-11-19
    • 56

    Description

      The backup_cursor_truncate_after test will always try setting the truncate after point to the top of oplog. However, that timestamp is "inclusive" meaning replication recovery will try to remove that document. If that oplog entry is also the checkpoint timestamp, that document is majority committed and cannot be removed. The test should omit that scenario when it occurs.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: