[SERVER-60870] Write automation test for read and writes after TenantMigration completes Created: 20/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-10-25, Server Serverless 2021-11-01, Server Serverless 2021-11-15
Participants:

 Description   

While working on SERVER-60599 it was decided to also add the following test cases :

  • Have a TenantMigration finish and return committed and then access in read / write. The count and insert commands (read and write) should not work since it should return "committed" and the mongos hasn't updated its routing table to route to the new owner (using commandFailedWithCode - ErrorCodes.TenantMigrationCommitted)
  • Have a TenantMigration started and then aborted. Then try to read and write (using count and insert) on the database. This should work (commandWorked should succeed) since the migration was aborted and therefor the owner hasn't changed. 

 



 Comments   
Comment by Githook User [ 29/Oct/21 ]

Author:

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

Message: SERVER-60870 adding automation test case for read/write access after
Branch: master
https://github.com/mongodb/mongo/commit/fde6bbbd32c8385a954ecb5e27b40aba12541ba6

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