In some situations migration that happens between two operations can cause first operation's GLE result to be returned to GLE call after second operation.
Running attached js file like so (omitting startup and shutdown lines):
mongo --nodb dupBad2.js | grep -v "^ m39" | grep -v "^ m30"
Number of successful updates on node: 0
successful update on node on A
n=0,
updatedExisting=true,
err=E11000 duplicate key error index: test.trans.$owner_1 dup key: { : 1234567890 }
successful update on node on B
n=0,
updatedExisting=true,
err=E11000 duplicate key error index: test.trans.$owner_1 dup key: { : 1234567890 }
Number of successful updates on node: 2
- is depended on by
-
PYTHON-469 Possible to get: E11000 duplicate key error index ... on a remove
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-