[SERVER-8245] logging cleanup: review severity of sharding log messages Created: 18/Jan/13  Updated: 06/Dec/22  Resolved: 19/Apr/18

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

Type: Task Priority: Major - P3
Reporter: Andre de Frere Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: polish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-5092 Better named logging with tracing Closed
Related
related to SERVER-30841 Lower the amount of metadata refresh ... Closed
is related to DOCS-1019 More detailed documentation on Shardi... Closed
Assigned Teams:
Sharding
Sprint: Server 2.7.4, Server 2.7.5, Server 2.7.6
Participants:

 Description   

Some log messages to do with sharding are too verbose. These fill the logs and don't make much sense to the end user, as the internals of shard versions etc are not known. Increasing their logging level will clean up the logs and prevent misattributed issues.

Messages such as "could not initialize cursor across all shards because : stale config detected for ns"



 Comments   
Comment by Gregory McKeon (Inactive) [ 19/Apr/18 ]

Closing this meta-ticket, will refile smaller tickets as needed.

Generated at Thu Feb 08 03:16:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.