[SERVER-26888] profile_find.js should filter profile entries for query Created: 02/Nov/16 Updated: 19/Nov/16 Resolved: 04/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Query 2016-11-21 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
profile_find.js can fail erroneously when it assumes the latest profiler entry is for a query it ran. Sometimes the latest profile entry is for a killcursors command that is run by the shell. We should change profile_find.js to filter the profiler entries for {op: "query"}. |
| Comments |
| Comment by Githook User [ 04/Nov/16 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |