[SERVER-7967] In sharded clusters on failed insert GLE sometimes returns null err field Created: 17/Dec/12 Updated: 15/Feb/13 Resolved: 18/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.2.2, 2.3.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | 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: | see attached |
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When doing an insert into a sharded collection because of Before fix for assert failed : Insert of a duplicate record after split/migrate did not create correct GLE{ , |
| Comments |
| Comment by Asya Kamsky [ 18/Dec/12 ] |
|
Duplicate of |
| Comment by Asya Kamsky [ 18/Dec/12 ] |
|
Okay, while this might be considered a special case of However, since without those changes |