[SERVER-57276] Capture max/min percent complete in FTDC metrics as seen by the commit monitor Created: 28/May/21  Updated: 29/Oct/23  Resolved: 16/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.4, 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: Junhson Jean-Baptiste (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-234-T-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-14654 [Server] Document min/max operation t... Backlog
Related
is related to SERVER-57100 Investigate critical section timeout ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding 2021-07-12, Sharding 2021-07-26
Participants:
Story Points: 1

 Description   

This tickets adds a new graph to FTDC. We want to display the maximum and minimum remaining operation time reported to the commit monitor.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 22/Sep/21 ]

Author:

{'name': 'Junhson Jean-Baptiste', 'email': 'junhson.jean-baptiste@mongodb.com', 'username': 'junhsonjb'}

Message: SERVER-57276 Capture max/min percent complete in FTDC metrics as seen by the commit monitor

(cherry picked from commit 181a798b2f6bf25cbab21050a34ab39e30fd8669)
Branch: v5.0
https://github.com/mongodb/mongo/commit/a363054396df92af8da681d3743df9a17f5aadbb

Comment by Githook User [ 15/Jul/21 ]

Author:

{'name': 'Junhson Jean-Baptiste', 'email': 'junhson.jean-baptiste@mongodb.com', 'username': 'junhsonjb'}

Message: SERVER-57276 Capture max/min percent complete in FTDC metrics as seen by the commit monitor
Branch: master
https://github.com/mongodb/mongo/commit/181a798b2f6bf25cbab21050a34ab39e30fd8669

Comment by Bruce Lucas (Inactive) [ 03/Jun/21 ]

Makes sense, thanks.

Comment by Max Hirschhorn [ 02/Jun/21 ]

The resharding coordinator receives one value at a single time instant from each recipient shard of the estimate for how long resharding has remaining. I believe the idea on this ticket to summarize those estimates as Min(all recipient shards) and Max(all recipient shards) in FTDC. The Max(all recipient shards) is also used by the resharding coordinator to flip of switch of when to engage the critical section and begin blocking writes.

I believe already have the Max(all recipient shards) as remainingOperationTimeEstimated in $currentOp and so we could a similar name for serverStatus/FTDC.

remainingOperationTimeEstimatedMillis: int64
minShardRemainingOperationTimeEstimatedMillis: int64

(not attached to these names to whoever picks this ticket up)

These metrics would be listed under the "shardingStatistics.resharding" object we already created during the resharding project.

Comment by Bruce Lucas (Inactive) [ 02/Jun/21 ]

I assume this means to add some new metrics to serverStatus? Can you please sketch out the proposed new metrics, e.g. what path in serverStatus. Also, can you clarify the semantics - min and max over what? Is this min at a given point in time over some set of numbers, or is it the min and max of a single number over a time range? If the later, what time range? Or is it something else?

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