[SERVER-12360] new sharded GLE must correctly emulate mongod GLE for legacy support Created: 14/Jan/14 Updated: 02/Aug/18 Resolved: 17/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The current implementation of getLastError in mongos does not correctly aggregate write concern errors (any write concern error always aborts the entire GLE). Better supporting this mode is needed for backwards compatibility and so the bulk api is able to downconvert against mongos 2.6 correctly (though this should be rare and weird). |
| Comments |
| Comment by Greg Studer [ 17/Jan/14 ] |
|
Fixed by: Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: (+ bugfixes on the same ticket) Though JIRA slug was for the other ticket. |