[SERVER-12791] Unable to killOp count stage of query execution Created: 19/Feb/14 Updated: 10/Dec/14 Resolved: 24/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | killop, query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
When running a count after setting the kill flag, the count will reach completion without being killed. |
| Comments |
| Comment by Githook User [ 24/Feb/14 ] |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: |
| Comment by hari.khalsa@10gen.com [ 24/Feb/14 ] |
|
This actually works. The interrupt checking is a layer above the count stage iteration. Every stage is wrapped in a PlanExecutor and/or Runner and that is where we check for an interrupt. |
| Comment by Eric Milkie [ 19/Feb/14 ] |
|
A test has been proposed that essentially inserts a bunch of documents, sets the kill flag, and then runs a Count PlanStage and checks to see that it doesn't reach the end before checking the flag. |
| Comment by Eric Milkie [ 19/Feb/14 ] |
|
Just in case Hari is OOO, can you post reproduction steps? |