[SERVER-12358] Add query plan history and logging Created: 14/Jan/14 Updated: 10/Dec/14 Resolved: 24/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Diagnostics, Logging, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Things exit the cache for: Let's log when this happens w/level...1. The query optimizer currently generates a query plan which is cached and re-used based on the normalized "shape" of the query predicate and sort criteria. It would be useful to be able to identify plans by id (e.g., hash value) for tracking, hinting and logging.
|
| Comments |
| Comment by Githook User [ 24/Jan/14 ] | |||||||||||||
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: | |||||||||||||
| Comment by Githook User [ 24/Jan/14 ] | |||||||||||||
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: | |||||||||||||
| Comment by Eric Milkie [ 21/Jan/14 ] | |||||||||||||
|
Currently the server is very noisy when I run it with a simple insert and remove:
This message should probably not be a warning. |