[SERVER-73811] Ignore duplicate key errors caused by bulk inserts with concurrent movePrimary Created: 09/Feb/23  Updated: 29/Oct/23  Resolved: 09/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: PM-2144-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-20
Participants:
Linked BF Score: 35

 Description   

Retryable writes may not work properly when performed on a shard involved as originator of a movePrimary operation. In this scenario, insert operations could be performed twice causing duplica key errors.
 
This is a known bug (SERVER-32113) which will be resolved in the context of the Online movePrimary project. The goal of this ticket is to implement a workaround to initializate the document snapshot of some collections using in move_primary_with_crud.js. A temporary solution (valid for this ticket) could be ignore these errors.



 Comments   
Comment by Githook User [ 09/Feb/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-73811 Ignore duplicate key errors caused by bulk inserts with concurrent movePrimary
Branch: master
https://github.com/mongodb/mongo/commit/54ab34d1019ace3b12d641af9facce797e7e71ed

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