[SERVER-50871] Add logging to SessionCatalogMigrationDestination to make it easier to diagnose if it hangs Created: 10/Sep/20  Updated: 29/Oct/23  Resolved: 22/Jan/21

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

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

Issue Links:
Backports
Problem/Incident
causes SERVER-61105 The sessions migration logic during m... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2, v4.0, v3.6
Sprint: Sharding 2020-09-21, Sharding 2020-10-05, Sharding 2020-10-19, Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2021-01-25, Sharding 2021-02-08
Participants:

 Comments   
Comment by Githook User [ 22/Jan/21 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-50871 Add logging to SessionCatalogMigrationDestination to make it easier to diagnose if it hangs
Branch: master
https://github.com/mongodb/mongo/commit/468bd494c8a7451b0d28eef4662a9b78b785cd4f

Comment by Esha Maharishi (Inactive) [ 25/Nov/20 ]

The cr above is LGTM'd, but when I tried submitting it I found a unit test that also needs to be updated (EVG patch).

I am putting this back on the sharding backlog - it would be an easy ticket for a neweng to pick up.

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