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

resharding_collection_cloner_resuming.js relies on history but doesn't set a minFetchTimestamp

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Sharding 2021-02-22, Sharding 2021-03-08
    • 20
    • 1

    Description

      Resharding writes a `minFetchTimestamp` value to the resharding document which has the side-effect of pinning history in the storage engine.

      However, the `testReshardCloneCollection` command does not execute the code to write a minFetchTimestamp. Thus there's no guarantee the oldest timestamp will keep the history necessary for the command to complete successfully, resulting in spurious test failures.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: