[SERVER-64022] Reduce Shard Merge logging Created: 26/Feb/22  Updated: 03/Mar/23  Resolved: 03/Mar/23

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

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-57991 Architecture Guide updates for PM-2353 Closed
Assigned Teams:
Serverless
Participants:

 Description   

Examine the logging we added for Shard Merge and remove messages we no longer need, or lower their severity. The goal is to reduce the volume of messages in Lobster that aren't helpful for diagnosing BFs, and reduce the volume of messages in Cloud log files that aren't helpful for diagnosing production issues.

TenantFileCloner is especially logorrheic, it doesn't need to announce every file and every batch of every aggregation cursor.


Generated at Thu Feb 08 05:59:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.