Fix test cases for snapshot reads without atClusterTime and for aborted migrations in tenant_migration_concurrent_reads_on_recipient.js

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2021-03-22
    • 24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      • Make sure that snapshot reads with atClusterTime in testDoNotRejectReadsAfterMigrationAbortedAfterReachingBlockTimestamp and testDoNotRejectReadsAfterMigrationAbortedAfterReachingBlockTimestamp get assigned read timestamp >= blockTimestamp.
      • Make testDoNotRejectReadsAfterMigrationAbortedAfterReachingBlockTimestamp test that if the migration aborts after returnAfterReachingTimestamp (blockTimestamp) is reached, the recipient keeps rejecting reads with atClusterTime < returnAfterReachingTimestamp (blockTimestamp) until the state doc is garbage collected. Currently, it tests that the recipient stops rejecting reads after the migration aborts.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: