[SERVER-82060] Consider adding more logging to external_data_source.js and writeToPipeObjectsAsync() shell function Created: 10/Oct/23  Updated: 29/Oct/23  Resolved: 13/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

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

Issue Links:
Depends
Assigned Teams:
Query Integration
Backwards Compatibility: Fully Compatible
Sprint: QI 2023-10-16
Participants:
Linked BF Score: 135

 Description   

Given that external_data_source.js fails very rarely as we add more test jobs, it would be helpful to add some more logging so that we can quickly identify the same failure pattern when there's thread resource shortage.

We have testSimpleAggregationsOverExternalDataSource() function in external_data_source.js and this function executes many test cases. We can add progress logging for each test case.

And we can add INFO-level logging to writeToPipeObjectsAsync shell function. This function is called in the context of tests and so it's safe to add INFO-level logging.

Other than this, we should add requires_external_data_source exclusion tag to newly failing build variants which are enterprise-rhel80-fixed-service-executor-64-bit and linux-x86-dynamic-grpc-suggested just like this commit.



 Comments   
Comment by Githook User [ 13/Oct/23 ]

Author:

{'name': 'Yoonsoo Kim', 'email': 'yoonsoo.kim@mongodb.com', 'username': 'yun-soo'}

Message: SERVER-82060 Add more logging to help test failure debugging
Branch: master
https://github.com/mongodb/mongo/commit/d36da446239135dc052bb3cdb7d0b16089a4a13a

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