[SERVER-41996] Improve PlanExecutor error logging Created: 28/Jun/19  Updated: 29/Oct/23  Resolved: 01/Jul/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.2.1, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Anton Korshunov Assignee: Anton Korshunov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-51702 Log commands together with errors upo... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Query 2019-07-01, Query 2019-07-15
Participants:
Linked BF Score: 11

 Description   

When a PlanExecutor fails while executing a query command, such as `find` or 'getMore', we log just a generic message using using the ERROR severity to indicate that a failure has occurred, along with some basic explain output. We do not include an error message and an error code to help diagnose the failure. This should be improved to always log the error code and the message.



 Comments   
Comment by Githook User [ 23/Aug/19 ]

Author:

{'username': 'antkorsh', 'email': 'anton.korshunov@mongodb.com', 'name': 'Anton Korshunov'}

Message: SERVER-41996 Improve PlanExecutor error logging

(cherry picked from commit 9202b2024c943984bf6436c2110ef0220bf0927c)
Branch: v4.2
https://github.com/mongodb/mongo/commit/12b6cf2aa0935c8977b106f6e48bf13abf00f0be

Comment by Githook User [ 01/Jul/19 ]

Author:

{'name': 'Anton Korshunov', 'email': 'anton.korshunov@mongodb.com', 'username': 'antkorsh'}

Message: SERVER-41996 Improve PlanExecutor error logging
Branch: master
https://github.com/mongodb/mongo/commit/9202b2024c943984bf6436c2110ef0220bf0927c

Generated at Thu Feb 08 04:59:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.