[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: |
|
||||||||||||||||||||
| 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. |