[SERVER-37914] Consider increasing the NETWORK component in Sharding suites to 3 Created: 02/Nov/18  Updated: 06/Dec/22  Resolved: 09/Nov/18

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

Type: Improvement Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

In the fallout from SERVER-37913, esha.maharishi and I ruminated that it would help diagnose Sharding build failures if we increased the NETWORK component to verbosity 3. This would allow us to see what nodes are communicating when sending and receiving commands, allowing us to see for example which node in a config server returned a particular response.



 Comments   
Comment by Gregory McKeon (Inactive) [ 09/Nov/18 ]

We're worried about how much additional logging this will produce, so not doing for now.

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