[SERVER-44167] Add OperationKey to OperationContext and allow "clientOperationKey" field with commands Created: 22/Oct/19  Updated: 29/Oct/23  Resolved: 02/Jan/20

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-44164 Create the killOperations command Closed
Related
related to SERVER-46255 establishCursors/AsyncRequestsSender ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2019-11-18, Service Arch 2019-12-02, Service Arch 2019-12-16, Service Arch 2019-12-30, Service Arch 2020-01-13
Participants:

 Description   

OperationKey is a uuid that will optionally be attached to the OperationContext object. It may be set by an internal client connection (or a testing user) via the field "clientOperationKey". This work will also involve adding an unordered_map to ServiceContext to allow quick lookup of an OperationContext by OperationKey.



 Comments   
Comment by Githook User [ 31/Dec/19 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@mongodb.com', 'username': 'bcaimano'}

Message: SERVER-44167 Added ability to kill operations by key

There are two patches here really. One of which makes killOp fast to use
and visible. The other adds OperationKey to various places and maps it
to an internal OpId.
Branch: master
https://github.com/mongodb/mongo/commit/aa7260c8f699c3c691f836bf2286606b2a8eac93

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