[SERVER-19920] Duplicate Key Error on Upsert with multi processes Created: 13/Aug/15 Updated: 14/Aug/15 Resolved: 13/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | memorybox | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1. run test_mongo_update.py it will raise duplicate key error |
||||||||
| Participants: | |||||||||
| Description |
|
Hi, all I just got a weird error sent through from our applcation: when i updated with two processes, it was complaining of a duplicate key error on a collection with a unique index on it, but the operation in question was an upsert. case code(test_mongo_update.py):
When i run script with two processes, Pymongo Exception:
Env:
mongo.conf
PS: I retried the same case in MMAPV1 storage engine, it works fine, why? I've asked this same issue in StackOverflow (http://stackoverflow.com/questions/31962539/duplicate-key-error-on-upsert-with-multi-processesmongo-3-0-4-wiredtiger) and in the mongodb-user mailing list I found something related here: but after this bug fix, it cases this error, so it looks like this bug is not fixed completely. Cheers |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 13/Aug/15 ] |
|
This is a duplicate of Please read those for more information. |