Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
ALL
-
Dev Tools 2020-03-09, Dev Tools 2020-03-23
Description
It's obvious we're missing a layer of hierarchy in the structure.
The group of repeating keys (resourceId,granted,pending) should instead be the keys of a subobject created for each lock in the bucket.
existing (bad) format:
// add an element to result object:
|
// "lockInfo": [
|
// // for each nonempty bucket in LockManager, add a suboject.
|
// {
|
// "resourceId": <string>,
|
// "granted": [ {}, ... ], // array of lock requests
|
// "pending": [ {}, ... ], // array of lock requests
|
//
|
// // this triple of repeated keys are used to represent each lock in a bucket
|
// "resourceId": <string>,
|
// "granted": [ {}, ... ], // array of lock requests
|
// "pending": [ {}, ... ], // array of lock requests
|
//
|
// ...
|
// },
|
// ...
|
// ]
|
|
Attachments
Issue Links
- depends on
-
SERVER-46360 Hang analyzer json logging improvement
-
- Closed
-
- is depended on by
-
DOCS-11516 document lockInfo command
-
- Closed
-