[SERVER-14643] Reason for query failure due to --notablescan should be included in log messages Created: 21/Jul/14 Updated: 11/Nov/19 Resolved: 11/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Querying |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | David Percy |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-11-04, Query 2019-11-18 |
| Participants: |
| Description |
|
When a query fails due to running mongod with --notablescan, the log message should indicate that the query failure was due to running with --notablescan. Setup:
1) A normal find against a missing index will report which attribute is being queried, but not that it is failing due to --notablescan: Prior to 2.6, this was logged:
After 2.6:
This impacts all clients of the query system: distinct, m/r, agg, count, etc. |
| Comments |
| Comment by Githook User [ 11/Nov/19 ] |
|
Author: {'username': 'dpercy', 'email': 'david.percy@mongodb.com', 'name': 'David Percy'}Message: |
| Comment by Asya Kamsky [ 27/Feb/19 ] |
|
Would like to nominate for quick win candidate. |
| Comment by Asya Kamsky [ 27/Feb/19 ] |
|
A charts user just ran into this - charts just runs agg with $limit:20 to sample some documents to get their fields. Very cryptic error message and hard to find. |