[SERVER-52774] Periodically persist metrics about resharding on shards Created: 11/Nov/20  Updated: 06/Dec/22  Resolved: 20/Jan/21

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: PM-234-M3, PM-234-O-unspecialized, PM-234-T-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52773 Add "resharding" section to server st... Closed
Duplicate
duplicates SERVER-53915 Persist total number of oplog entries... Closed
Assigned Teams:
Sharding
Participants:
Story Points: 2

 Description   

The persisted counters will be used to surface estimates about the resharding operation in $currentOp. Persisting and replicating the metrics enables $currentOp to report these estimates following a primary failover or server restart.

  • The metrics from the "resharding" section in server status can be a starting point for the ones to persist. It should also be possible to reinitialize the in-memory counters from the persisted state.
  • The counters for the number of successful, failed, and user-canceled resharding operations need not be persisted. The counters therefore need not be persisted on the config server.

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