[SERVER-17281] Segfault during id_hack FSM test Created: 13/Feb/15 Updated: 18/Sep/15 Resolved: 17/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Querying, Replication |
| Affects Version/s: | 3.1.0 |
| Fix Version/s: | 3.0.0-rc9, 3.1.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Charlie Swanson | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Steps To Reproduce: | Occasionally reproduce locally. The easiest way to run the same test is to modify fsm_all_replication.js to only include fsm_workloads/yield_id_hack.js. |
| Participants: |
| Description |
|
FSM test fails in a replicated environment with this failure. The FSM test interleaves updates, deletes, inserts, and querying with multiple threads. The query used is specifically on _id, to use the ID_HACK query phase.
|
| Comments |
| Comment by Githook User [ 17/Feb/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |
| Comment by Githook User [ 17/Feb/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit 48e7b856f2b336537ca560ae9ab1740a293b53b9) |
| Comment by David Storch [ 17/Feb/15 ] |
|
This issue affects MMAP v1 only. IDHackStage::invalidate() is using the wrong OperationContext pointer to force-fetch invalidated documents. It is attempting to use its own OperationContext pointer, but this pointer was set to NULL on saveState. Instead, it should use the one passed as an argument to invalidate(). I audited the query execution stages to see if any other stage suffers from the same bug, but I did not find any problems. |