[SERVER-76588] originatingCommand is inconsistent with planCacheKey in slow log messages Created: 27/Apr/23  Updated: 11/Aug/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alexander Ignatyev Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Optimization
Operating System: ALL
Sprint: QO 2023-05-15, QO 2023-05-29, QO 2023-06-12
Participants:
Case:

 Description   

In HELP-44479 we observed that the planCacheKey logged for some commands were inconsistent with originatingCommand.
It might happen that logged originatingCommand or planCache were stale.



 Comments   
Comment by Alexander Ignatyev [ 20/Jun/23 ]

david.storch@mongodb.com updated

Comment by David Storch [ 20/Jun/23 ]

anton.korshunov@mongodb.com my recollection of our discussion about this is that the ticket title is inaccurate. Can we either close this ticket or fix the title?

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