-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
It could be helpful to have a dump of CurOp info when debugging lock acquisition timeouts. One way of doing this could be issuing a signal like SIGUSR2 in conjunction with some global flag that will tell threads to dump their own CurOp info.
As mentioned in SERVER-71521, ideally CurOp would contain info on:
- what is the current running operation
- what is it currently doing at the moment
- if it is waiting on something, how long has it been waiting, and how long did it spend on each step of its operation until now
- is related to
-
-
- Closed
-
-
SERVER-95489 Explore if we can use curOp to log all active operations if we fail to acquire the RSTL during step up/step down
-
- Open
-
-
-
- Closed
-