[SERVER-48174] Add log component and LOGV2 messages in server to measure latency of migration protocol stages Created: 12/May/20  Updated: 29/Oct/23  Resolved: 25/Jun/20

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

Type: Task Priority: Major - P3
Reporter: Alexander Taskov (Inactive) Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-48172 Add tracking of total latency in Clus... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-06-01, Sharding 2020-06-15, Sharding 2020-06-29
Participants:

 Description   

Instrument the C++ code to measure:

total latency = majority commit wait on recipient                    (1)
                      + migration commit                                               (2)
                      + post-migration commit refresh on the shard   (3)
                      + post-migration commit refresh on the router  (4)
                      + unnamed portion of operation latency             (5)



 Comments   
Comment by Githook User [ 25/Jun/20 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}

Message: SERVER-48174 Add log component and LOGV2 messages in server to measure latency of migration protocol stages
Branch: master
https://github.com/mongodb/mongo/commit/47dcbeba765b04a829be9c27289e152e24e1a855

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