[SERVER-60771] Suppress heartbeat log messages in $lookup execution tests Created: 18/Oct/21  Updated: 29/Oct/23  Resolved: 19/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0, 5.1.0-rc2

Type: Bug Priority: Major - P3
Reporter: Hana Pearlman Assignee: Hana Pearlman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.1
Participants:
Linked BF Score: 50

 Description   

The test is failing because the server maintains an internal buffer of size 1024, and it seems that 1103 log lines were logged after the local read occurred, so we fail to find the local read log. We can decrease some of the logging that's happening, and that should help avoid the issue, following the example from SERVER-58166. We can also retry parts of the test that fail if we detect the buffer may have rotated past lines we are looking for. 

An alternative is to make sure the logs we're interested in are not rotated off the buffer by adding a special workaround to never throw away logs matching some specified regex. I think this would be overly complicated to implement.



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

Author:

{'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}

Message: SERVER-60771: Suppress heartbeat log messages in $lookup execution tests

(cherry picked from commit dd04992030d53e2b52fc83261f51e119a134de58)
Branch: v5.1
https://github.com/mongodb/mongo/commit/dabba0b61a1be7d327f40e4ac9fd932a90d8b3fc

Comment by Githook User [ 19/Oct/21 ]

Author:

{'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}

Message: SERVER-60771: Suppress heartbeat log messages in $lookup execution tests
Branch: master
https://github.com/mongodb/mongo/commit/dd04992030d53e2b52fc83261f51e119a134de58

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