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

XMLWordPrintableJSON

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

      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.

            Assignee:
            Daniel Gottlieb (Inactive)
            Reporter:
            Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: