[SERVER-55050] Fix test cases for snapshot reads without atClusterTime and for aborted migrations in tenant_migration_concurrent_reads_on_recipient.js Created: 08/Mar/21  Updated: 29/Oct/23  Resolved: 10/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: pm-1791_non-cloud-blocking
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-03-22
Participants:
Linked BF Score: 24

 Description   
  • 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.


 Comments   
Comment by Githook User [ 10/Mar/21 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-55050 Fix test cases for snapshot reads without atClusterTime and for aborted migrations in tenant_migration_concurrent_reads_on_recipient.js
Branch: master
https://github.com/mongodb/mongo/commit/d18148295e08cc20dc57f734b15cd699a9c825eb

Generated at Thu Feb 08 05:35:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.