[SERVER-50976] Add currentOp reporting for ReshardingCoordinatorService Instances Created: 16/Sep/20  Updated: 29/Oct/23  Resolved: 05/Feb/21

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Amirsaman Memaripour
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-O-unspecialized, PM-234-T-autocommits, PM-234-T-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49243 Add optional currentOp output for Pri... Closed
Documented
is documented by DOCS-14197 Investigate changes in SERVER-50976: ... Closed
Related
related to SERVER-50978 Add currentOp reporting for Reshardin... Closed
is related to SERVER-51021 Add currentOp reporting for Reshardin... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-02-22
Participants:
Story Points: 1

 Description   

SERVER-49243 Adds a mechanism by which PrimaryOnlyServices can report information about their running Instances in currentOp() output.  This ticket is to decide whether or not to use that functionality to report information about ReshardingCoordinatorService Instances in currentOp, and to add that functionality if so.



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

Author:

{'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}

Message: SERVER-50976 Add currentOp reporting for ReshardingCoordinatorService Instances
Branch: master
https://github.com/mongodb/mongo/commit/2bdf8c73962d53a98a8e048d10d718e6858e944b

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