[SERVER-51423] Test that a bulk write returns ok for the writes that complete before a migration starts blocking and TenantMigrationCommitted for the ones that don't Created: 07/Oct/20  Updated: 29/Oct/23  Resolved: 23/Oct/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-A
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-19, Sharding 2020-11-02
Participants:

 Description   

MongoDB has a "bulk write" API that allows sending an array of writes in a single command.

The bulk write can be "ordered" or "unordered", and returns an array of writeErrors for the writes that failed.

When a bulk write is issued concurrently with a tenant migration, some of the writes may succeed before the migration starts blocking, and the remaining writes should return a TenantMigrationCommitted error in the writeErrors array.

This ticket is to add a test that verifies this, and to write sample logic for parsing the writeErrors array and retrying only the writes that returned TenantMigrationCommitted against the recipient (and confirming they succeed against the recipient).



 Comments   
Comment by Githook User [ 22/Oct/20 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-51423 Test that a bulk write returns ok for the writes that complete before a migration starts blocking and TenantMigrationCommitted for the ones that don't
Branch: master
https://github.com/mongodb/mongo/commit/e428dcb7b9bc3d6b39c4a0de4db46c75441c9d64

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