[DOCS-3699] Warnings around notablescan Created: 03/Jul/14 Updated: 16/Mar/15 Resolved: 28/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
http://docs.mongodb.org/v2.4/reference/configuration-options/#notablescan |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 24 weeks, 1 day ago | ||||||||
| Description |
|
There are a number of places within MongoDB where running with --notablescan will break things. We should confirm the specific impacts of running with this on a live system and provide warnings about enabling this option to end users. Historically the advice we have given to our customers has been "only use this in Dev as a way to catch poor queries" |
| Comments |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 28/Aug/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |