[SERVER-61036] Write automation test for findAndModify happening while a TenantMigration is in a blocking state Created: 27/Oct/21  Updated: 29/Oct/23  Resolved: 07/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Mathis Bessa Assignee: Mathis Bessa
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2021-11-01, Server Serverless 2021-11-15
Participants:

 Description   

While working on SERVER-60599 it was decided to test the case of using the findAndModifyCmd which doesn't require server changes in order to get into that state.

The test case should cover the following :

  • Start a tenant migration and enter a blocking state.
  • While the migration is in a blocking state, run asynchronously findAndModifyCmd
  • When joining the thread that ran the command findAndModifyCmd, make sure the command failed with code "TenantMigrationAborted"


 Comments   
Comment by Githook User [ 01/Nov/21 ]

Author:

{'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}

Message: SERVER-61036 adding automation test for findAndModifyCmd after migrat
Branch: master
https://github.com/mongodb/mongo/commit/4a2038826d71171cf4f1fa1ec5afc01697d36b1f

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