[SERVER-16807] Update on invalid loc fails in concurrent circumstances Created: 12/Jan/15 Updated: 23/Jan/15 Resolved: 15/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.8.0-rc4 |
| Fix Version/s: | 3.0.0-rc6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Balsano | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
If you're trying to update the same document from multiple threads and looking it up by indexed _id, a yield to load the document from disk will result in an invalid document location in the UpdateStage. First turned up on MCI windows build in fsm_all.js, log is attached.
|
| Comments |
| Comment by Githook User [ 15/Jan/15 ] |
|
Author: {u'username': u'jrbalsano', u'name': u'Jonathan Balsano', u'email': u'jonathan.balsano@10gen.com'}Message: Necessary changes to concurrency testing framework to support the fix Closes #909 Signed-off-by: Benety Goh <benety@mongodb.com> |
| Comment by Githook User [ 15/Jan/15 ] |
|
Author: {u'username': u'jrbalsano', u'name': u'Jonathan Balsano', u'email': u'jonathan.balsano@10gen.com'}Message: Necessary changes to concurrency testing framework to support the fix Closes #909 Signed-off-by: Benety Goh <benety@mongodb.com> |
| Comment by Githook User [ 15/Jan/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |