[SERVER-48529] Delete unused PlanCache::feedback() mechanism Created: 01/Jun/20  Updated: 29/Oct/23  Resolved: 02/Jun/20

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.7.0, 4.4.3

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-13686 Investigate changes in SERVER-48529: ... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Query 2020-06-15
Participants:
Linked BF Score: 0

 Description   

In previous versions, the PlanCache tracked the score associated with a cache entry for several historical executions of the cached plan. These scores were then surfaced via the planCacheListPlans comment, which was deprecated in 4.2 and removed in 4.4. The number of historical executions tracked was controlled by the internalQueryCacheFeedbacksStored setParameter.

Since this information is no longer surfaced by the replacement for planCacheListPlans (the $planCacheStats agg stage), the code for tracking this "feedback" information can be deleted. The internalQueryCacheFeedbacksStored setParameter can also be deleted.



 Comments   
Comment by Githook User [ 19/Nov/20 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-48529 Delete PlanCache::feedback() and related code

(cherry picked from commit d82c036d05a7898dd17ca219f626cf4fd4759c79)
Branch: v4.4
https://github.com/mongodb/mongo/commit/9833b6ed1b74d58af01d5e6eaa62ca8d7ceb3d34

Comment by Githook User [ 02/Jun/20 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-48529 Delete PlanCache::feedback() and related code
Branch: master
https://github.com/mongodb/mongo/commit/d82c036d05a7898dd17ca219f626cf4fd4759c79

Generated at Thu Feb 08 05:17:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.