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

In oplog truncate with WT, don't use a start key

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • v3.6, v3.4
    • Storage 2018-01-15, Storage 2018-01-29
    • 0

    Description

      A user experienced a case where oplog entries were unexpectedly found at the beginning of the oplog after later records were truncated.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. WT-3946 Truncate segfault with a NULL start cursor

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31924 OplogStones can capture record ids to truncate out of order

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

          Activity

            People

              michael.cahill@mongodb.com Michael Cahill (Inactive)
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: