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

Rename collection on a secondary can set the collection minimumVisibleSnapshot timestamp backwards in time after a background index build's ghost commit cluster time timestamp

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.8, 4.1.10
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2019-03-25
    • 63

    Description

      AutoGetCollection will throw if a caller tries to access the collection at a point-in-time earlier than the min visible timestamp. Because renameCollection sets the min visible timestamp back in time, callers can now access the collection at an earlier time than an index build completed. This can hit the DEV (debug only) block in IndexCatalog::numIndexesReady and invariant; or allow callers that expect an index build to be complete to find no ready index because we filter out ready indexes based on commit timestamp, which can fail our testing that primaries and secondaries have the same number of indexes.

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: