[SERVER-70939] Shard split write-during-aborted tests expect wrong outcome for writes Created: 28/Oct/22  Updated: 29/Oct/23  Resolved: 07/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Matt Broadstone Assignee: Matt Broadstone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2022-11-14
Participants:
Linked BF Score: 35

 Description   

Access blockers will always reject a write during a tenant migration with either TenantMigrationAborted or TenantMigrationCommitted. We have a test that performs a number of writes during a tenant migration, and then expects the result to be OK which is impossible. It's likely that these writes have been completing after the split has been aborted, which is why we haven't seen a failure in the last year.



 Comments   
Comment by Githook User [ 07/Nov/22 ]

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-70939 Refactor split writes-during-aborted test
Branch: master
https://github.com/mongodb/mongo/commit/bb5aca605f73cc6842a9dc0a30bca07f185f6931

Generated at Thu Feb 08 06:17:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.