[SERVER-19600] Upsert results in E11000 duplicate key error Created: 27/Jul/15 Updated: 14/Aug/15 Resolved: 30/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yury Michurin | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | concurrency | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 14.04 3.16.0-43 64bit, 16GB RAM, i5-4690 CPU @ 3.50GHz |
||
| Issue Links: |
|
||||||||||||
| Operating System: | Linux | ||||||||||||
| Steps To Reproduce: | |||||||||||||
| Participants: | |||||||||||||
| Description |
|
I'm basically upserting documents that has random sid 1..100, and then update the hit counter on them. So the document looks like that: { 'sid': 23, 'status': 'active' 'hit': 12 }A timer changes the status field from 'active' to something else occasionally. That program runs successfully on mongodb 3.0.4 with MMAPv1 engine, but throws E11000 errors with wiredtiger. javascript code to replicate: It's a reduced case of my more complicated python code (pymongo 3.0.3), which has the same problem. expected result: actual result: Best regards, |
| Comments |
| Comment by Ivan Fioravanti [ 11/Aug/15 ] |
|
We are experiencing the same issue with C# client, I voted for |
| Comment by Ramon Fernandez Marina [ 30/Jul/15 ] |
|
Hi yurynix; you're right, this looks like a case of I'm going to close this ticket as a duplicate of Regards, |
| Comment by Yury Michurin [ 27/Jul/15 ] |
|
Ok, after further investigation, it looks like a duplicate of: I guess. |