[DOCS-6401] Updates to query plan revision as of 3.0.7/3.1.7 Created: 19/Oct/15  Updated: 11/Jan/17  Resolved: 11/Mar/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-3.0, mongodb-3.1.x
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-6372 Query Plans page is out of date Closed
is related to SERVER-15225 CachedPlanStage should execute for tr... Closed
is related to SERVER-17895 Server should not clear collection pl... Closed
is related to SERVER-20139 Enable CachedPlanStage replanning by ... Closed
Participants:
Days since reply: 7 years, 48 weeks, 5 days ago

 Description   

MongoDB 3.0.7 and 3.1.7 add two significant changes to historical query revision behaviour:

  • SERVER-17895 (Server should not clear collection plan cache periodically when write operations are issued)
  • SERVER-15225/SERVER-20139 (Enable CachedPlanStage replanning by default)

These should be reflected in the query plan revision notes: http://docs.mongodb.org/manual/core/query-plans/#query-plan-revision

  • SERVER-17895 removes: "The collection receives 1,000 write operations."
  • SERVER-20139 adds: "If the cost of the cached query plan is too high as compared to an alternative plan, the query planner switches to the more efficient plan and caches this choice for future use."


 Comments   
Comment by Ravind Kumar (Inactive) [ 11/Mar/16 ]

Fixed via DOCS-6372

Generated at Thu Feb 08 07:52:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.