[SERVER-46036] Increase logging verbosity for agg_out.js workload Created: 07/Feb/20  Updated: 19/Mar/20  Resolved: 19/Mar/20

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Randolph Tan
Resolution: Won't Fix Votes: 0
Labels: sharding-4.4-stabilization, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Sprint: Sharding 2020-04-06
Participants:
Linked BF Score: 9

 Description   

This is necessary to diagnose the linked BF.

We can signal to the test runner that we want to increase verbosity with the following:

Passing a flag to indicate that we want to increase logging in the workload's setup function, and indicate that we want to reset in the teardown function.

And then we can apply the command to each node via thesehttps://github.com/mongodb/mongo/blob/d436c1ef262ac8caa9d59406448d41e426134533/jstests/concurrency/fsm_libs/cluster.js#L275-L280 executeOnXNode functions.

The tricky part of the ticket is figuring out how to pipe this notion through the various parts of the FSM runner.


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