[SERVER-51702] Log commands together with errors upon plan executor failures Created: 16/Oct/20  Updated: 29/Oct/23  Resolved: 20/Oct/20

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.9.0

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

Issue Links:
Backports
Related
related to SERVER-41996 Improve PlanExecutor error logging Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2, v4.0, v3.6
Participants:
Linked BF Score: 0

 Description   

When the plan executor fails for some commands, starting from SERVER-41996 an error message is logged before propagating the exception (e.g. in those snippets for distinct and find).

While upon some failures it's easy to trace back which command caused the exception, tests with no sufficient logging or concurrent commands are making it difficult to map specific commands to errors.

Logging the original command together with the error message would allow to identify problems in a fast and effective way



 Comments   
Comment by Githook User [ 20/Oct/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-51702 Log commands together with errors upon plan executor failures
Branch: master
https://github.com/mongodb/mongo/commit/a3f636ad4471718fd48489d1507e7a01c9f5fe4b

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