-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0
-
Component/s: None
-
None
-
Query Execution
-
ALL
-
(copied to CRM)
When write_ops_exec::shouldRetryDuplicateKeyException() returns true, we retry findAndModify on DuplicateKey. I think the assumption is that the document didn't exist before the command starts. However, this assumption is false when the unique index is partial.
- is caused by
-
SERVER-47212 Retry full upsert path when duplicate key exception matches exact query predicate in findAndModify
- Closed
- related to
-
SERVER-95524 Understand why findAndModify upsert retry on DuplicateKey succeeds when it shouldn't
- Open