[SERVER-59758] findAndModify with upsert=true generates duplicate key errors Created: 02/Sep/21 Updated: 06/Dec/22 Resolved: 29/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gaël Jourdan-Weil | Assignee: | Backlog - Triage Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Server Triage
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
This is very similar to
Error:
Indexes
Commands run (though ReactiveMongo Scala):
In our use case, 8 commands are sent at the same time and sometimes we get 1 such error (not always).
Current document matching:
Is this expected? Am I missing something? We can add some retry mechanism in our code but I'd like to understand why the auto retry does not work.
Any comment will be appreciated. |
| Comments |
| Comment by Edwin Zhou [ 29/Sep/21 ] |
|
Thanks for following up! Given that we've discussed that this a risky backport, I will close this as a duplicate of Best, |
| Comment by Gaël Jourdan-Weil [ 28/Sep/21 ] |
|
|