[SERVER-7958] GLE on sharded cluster can return previous operation's lastError Created: 17/Dec/12 Updated: 11/Jul/16 Resolved: 19/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Write Ops |
| Affects Version/s: | 2.2.2, 2.3.1 |
| Fix Version/s: | 2.2.3, 2.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | 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 |
|
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): Number of successful updates on node: 0 successful update on node on A successful update on node on B Number of successful updates on node: 2 |
| Comments |
| Comment by auto [ 20/Dec/12 ] |
|
Author: {u'date': u'2012-12-20T03:19:18Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |
| Comment by auto [ 20/Dec/12 ] |
|
Author: {u'date': u'2012-12-20T03:19:18Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |
| Comment by auto [ 19/Dec/12 ] |
|
Author: {u'date': u'2012-12-18T05:00:53Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |
| Comment by auto [ 18/Dec/12 ] |
|
Author: {u'date': u'2012-12-18T05:00:53Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Asya Kamsky [ 18/Dec/12 ] |
|
fixed up test with asserts for multiple scenarios, covering the edge cases discovered in |