-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Server Tooling & Methods
Currently, the LockManager::dump method only displays the resource id's of global resources:
2019-04-23T15:24:31.890+0000 I - [initandlisten] Lock @ 0x7F51BC3F9600: {2305843009213693953: Global, 1} 2019-04-23T15:24:31.890+0000 I - [initandlisten] Lock @ 0x7F51BC3F9680: {2305843009213693954: Global, 2} 2019-04-23T15:24:31.890+0000 I - [initandlisten] Lock @ 0x7F51BC3F9700: {2305843009213693955: Global, 3}
Remembering what each global lock id corresponds to is a manual translation process that is easy to forget. It would be helpful if the dump displayed a string along with the numeric id that identified the lock type e.g. Global, RSTL, or PBWM.
- duplicates
-
SERVER-39860 Separate reporting of RSTL and PBWM locks metrics in serverStatus and currentOp
- Closed
- related to
-
SERVER-43910 include Client/OpCtx information in LockManager::dump() output
- Closed