[SERVER-60446] Update sharded lookup tests to avoid overwriting relevant log entries Created: 04/Oct/21  Updated: 29/Oct/23  Resolved: 05/Oct/21

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

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: 62

 Description   

The asserts are failing because the relevant logs are rotated off the server's buffer of log messages.

We set the verbosity on each shard to level 3. We should either modify just the verbosity level of query logs or find some other way to avoid overwriting the logs.

This definitely applies to sharded_lookup_execution and may apply to lookup_unionWith_subpipeline_local_read.



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

Author:

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

Message: SERVER-60446: Only increase log level for query in sharded lookup tests
Branch: v5.1
https://github.com/mongodb/mongo/commit/042f23a84bdbe5b937f63903c6c8c0239ac0385e

Comment by Githook User [ 05/Oct/21 ]

Author:

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

Message: SERVER-60446: Only increase log level for query in sharded lookup tests
Branch: master
https://github.com/mongodb/mongo/commit/83ab4ae6cc436ac73b69bd1e540736fffc3b3832

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