[SERVER-41778] Increase log verbosity of the COMMAND component to level 2 in jstestfuzz suites Created: 14/Jun/19  Updated: 11/Oct/19  Resolved: 11/Oct/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3 Required

Type: Improvement Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Raiden Worley (Inactive)
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09, Repl 2019-09-23, Repl 2019-10-07, STM 2019-10-17
Participants:

 Description   

In many jstestfuzz suites, it can often be difficult to determine exactly what command the client sent to the server, since there is often much obfuscation that occurs in the generated fuzzer files. In the case of certain failures, like a command that trips an invariant, seeing the full command object as it was received by the server would be very helpful. By increasing the verbosity of the "COMMAND" log component to level 2, we would be able to see all command requests and responses in the server logs. To start, we could consider adding this for all single threaded fuzzer suites, so as not to flood the logs too aggressively in concurrency suites that run many more operations. Eventually it might make sense to increase verbosity for concurrent fuzzer suites as well. These would include the following suites:

  • jstestfuzz.yml
  • jstestfuzz_interrupt.yml
  • jstestfuzz_interrupt_replication.yml
  • jstestfuzz_replication.yml
  • jstestfuzz_replication_continuous_stepdown.yml
  • jstestfuzz_replication_initsync.yml
  • jstestfuzz_replication_session.yml
  • jstestfuzz_sharded.yml
  • jstestfuzz_sharded_causal_consistency.yml
  • jstestfuzz_sharded_continuous_stepdown.yml
  • jstestfuzz_sharded_session.yml


 Comments   
Comment by Githook User [ 10/Oct/19 ]

Author:

{'name': 'Carl Worley', 'email': 'carl.worley@mongodb.com'}

Message: SERVER-41778 Increase log verbosity of the COMMAND component to level 2 in jstestfuzz suites
Branch: master
https://github.com/mongodb/mongo/commit/3060375e3b6db727d726bfc37ee50dda3196e30d

Comment by William Schultz (Inactive) [ 27/Sep/19 ]

Wasn't able to get around to this so I am handing it off to TIG.

Comment by William Schultz (Inactive) [ 23/Aug/19 ]

Started to look into this. One challenge is figuring out a way to increase the logComponentVerbosity for only the non-concurrent fuzzer suites. If we change the verbosity inside the test suite YAML file e.g. jstestfuzz.yml, then the changes will apply to the concurrent suites as well, since the concurrency versions of the suites use the same YAML test suite but just change the "--numClientsPerFixture" argument. We may be able to do this by specifying the logComponentVerbosity in the etc/evergreen.yml file instead.

Generated at Thu Feb 08 04:58:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.