[SERVER-61183] Improve logging on how the migration source cloner transitions from catchup to steady phase Created: 02/Nov/21  Updated: 29/Oct/23  Resolved: 05/Nov/21

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

Type: Improvement Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-11-15
Participants:

 Description   

It is not currently possible to keep track of the amount of untransferred  mod data as the migration protocol executes the catch up phase, making the troubleshooting of functional and performance issues more difficult.

An easy fix for this would consist in including estimatedUntransferredModsSize as part of the information currently logged through log IDs 21992/21993 and 5630700.



 Comments   
Comment by Githook User [ 05/Nov/21 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-61183 improve logging in migration source cloner
Branch: master
https://github.com/mongodb/mongo/commit/02d158c3b2dffbe90e84599739ca05563b5c378b

Comment by Paolo Polato [ 04/Nov/21 ]

kaloian.manassiev I will - but I was actually in the middle of opening a PR for this.

Comment by Kaloian Manassiev [ 04/Nov/21 ]

paolo.polato, can you add a little bit more context here for whoever picks that up. Unless you are doing it?

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