[SERVER-15102] dbCurrentOp should show used index Created: 31/Aug/14 Updated: 06/Dec/22 Resolved: 22/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | rgpublic | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
It would be very useful IMHO, if dbCurrentOp could show the index currently in use for a (possibly long running) query. This would make it so much easier to spot bad optimizer decisions (which there are plentiful of in 2.6, unfortunately) where a hint should be added to the query. |