[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: |
|
||||
| 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. |
| Comments |
| Comment by Githook User [ 09/Feb/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |