[DOCS-16200] [SERVER] Investigate changes in SERVER-34633: Allow $currentOp to retrieve operations from all members of each shard in a cluster Created: 13/Jun/23  Updated: 13/Nov/23  Resolved: 27/Sep/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kenneth Dyer
Resolution: Fixed Votes: 0
Labels: replication, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-34633 Allow $currentOp to retrieve operatio... Closed
Participants:
Days since reply: 34 weeks, 1 day ago

 Description   
Original Downstream Change Summary

This change adds an option to $currentOp stage. {$currentOp: {targetAllNodes: val}} where if val is true, currentOp outputs a document for every data bearing node for all shards. (If there are 3 shards, each a 3 node replica set, we will get 9 docs). If val is false, currentOp outputs a document for every shard.

Description of Linked Ticket

With the introduction of the $currentOp aggregation stage, users have the ability to obtain a list of operations running on Secondaries in a sharded cluster by setting the appropriate readPreference. However, this will only provide the operations from a single eligible Secondary in each shard, and the standard approach to more fine-grained targeting - using replica set tags - is both onerous and does not satisfactorily address this shortcoming.

Add a new flag to $currentOp which, if set, stipulates that it should target every data-bearing member in each shard and return an exhaustive list of all operations running anywhere in the cluster.


Generated at Thu Feb 08 08:14:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.