[SERVER-71521] Improve currentOp to include more progress info for read and crud operations Created: 21/Nov/22  Updated: 05/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-71520 Dump all thread stacks on RSTL acquis... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

When debugging client issues involving deadlock / slowness in replication failover, we often need to ask for a core dump in order to know what was happening (see SERVER-56756 and SERVER-71520). Ideally, we want currentOp to be able to give us an answer of "what are all of the current running operations, what are they currently doing at the moment, and for those waiting on something, how long have they been waiting, and how long did they spend on each step of their operation until now".
currentOp currently has a progress field for the progress of mapReduce or indexing operations. It would be nice if we can have the progress breakdown for crud/read operations as well. (We could also just start with something simple to provide info about which subsystem, e.g. Query, WT, each operation is currently in.)


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