[SERVER-37698] Lower logging verbosity for sharding_balance4.js Created: 22/Oct/18  Updated: 29/Oct/23  Resolved: 28/May/19

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-37674 Increase log level in sharding_balanc... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Comments   
Comment by Matthew Saltz (Inactive) [ 28/May/19 ]

Author:

{'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz', 'username': 'saltzm'}

Message: Revert "SERVER-37674 Increase logging verbosity for sharding_balance4.js"

This reverts commit 5b2179fb8f852c956d85a10d01dcae5c4ae4b0c2.
Branch: master
https://github.com/mongodb/mongo/commit/be431419dbc96abbfb08acc0578a040aba16eba1

Comment by Matthew Saltz (Inactive) [ 28/May/19 ]

The BF this was originally created for has not failed again since changing the logging, so the additional logging hasn't helped to diagnose anything. I guess I can remove the logging again and see if the failure occurs once the logging is gone, since it might be one of those cases where the timing change due to the logging has made the issue go away

Comment by Kaloian Manassiev [ 24/May/19 ]

matthew.saltz, see if the increased verbosity is still necessary and if not, revert the original change or close?

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