[SERVER-55914] Improve logging in session migration code Created: 08/Apr/21  Updated: 06/Dec/22  Resolved: 22/Aug/22

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

Type: Improvement Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Duplicate Votes: 0
Labels: sharding-nyc-subteam2, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-56186 Add counters in session migration code Closed
Related
is related to SERVER-56186 Add counters in session migration code Closed
Assigned Teams:
Sharding NYC
Sprint: Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09, Sharding 2021-08-23
Participants:
Story Points: 3

 Description   

As seen in recent HELP tickets, session migration comes up as a likely culprit for slow migrations. As it stands, significant logging doesn't exist in the session migration classes, even at a higher verbosity. Improving the logging story in these classes will help diagnose future problems.


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