-
Type: Task
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: mongotop
-
None
-
1
-
1,876
The mongotop --locks option only works with EOL servers (MongoDB 2.6 and older).
MongoDB 3.0 and newer no longer provide per-database locking information so this option always results in:
Failed: server does not support reporting lock information
I think the --locks option should be hidden or removed since this has no utility with non-EOL server versions.
- related to
-
TOOLS-391 mongotop --locks with 3.0 mongod should show helpful error message and stop
- Closed