[SERVER-1657] explain() can't be killed Created: 23/Aug/10 Updated: 19/Mar/13 Resolved: 12/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Dwight Merriman | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
if you do db.find().explain(), on a giant table, there is no way to ever kill it. you will see lines like the following in the currentOp output, with quickly incrementing getmore opid's > db.currentOp() ] |
| Comments |
| Comment by Andy Schwerin [ 12/Mar/13 ] |
|
No repro in 2.4.0-rc2. |