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

don't generate convertToCapped oplog entries

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.10
    • Storage
    • None
    • Fully Compatible
    • Storage 2017-07-10
    • 0

    Description

      convertToCapped is implemented as a temporary collection creation, insertion of all existing records and then rename-in-place. However, instead of using calling existing catalog-level operations and letting them deal with replication, convertToCapped has its own oplog entry and calls lower level operations directly while suppressing normal replication.

      This adds extra maintenance work and upgrade complexities for supporting UUIDs. Removing the special purpose code simplifies, fixes some potential unhandled error conditions (WriteConflictException) and allows for normal rollback.

      Attachments

        Issue Links

          Activity

            People

              geert.bosch@mongodb.com Geert Bosch
              geert.bosch@mongodb.com Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: