[DOCS-5887] Document that v3.0 no longer tracks time spent in locks Created: 21/Jul/15  Updated: 30/Oct/23  Resolved: 30/Oct/17

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Joanna Cheng Assignee: Stennie Steneker (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to TOOLS-391 mongotop --locks with 3.0 mongod shou... Closed
is related to TOOLS-1849 Remove the mongotop --locks option Accepted
Participants:
Days since reply: 6 years, 15 weeks, 2 days ago

 Description   

I think the most appropriate place is in the 3.0 release notes, but happy to defer to whatever is decided.

Then add a link or reference at http://docs.mongodb.org/manual/reference/program/mongotop/#cmdoption--locks

Right now the docs say

--locks returns an error when called against a mongod instance that does not report lock usage.

But it's not clear what kind of mongod instances don't report lock usage



 Comments   
Comment by Githook User [ 30/Oct/17 ]

Author:

{'email': 'stennie@cpan.org', 'name': 'Stephen Steneker', 'username': 'stennie'}

Message: DOCS-5887: mongotop --locks is only supported for 2.6 and older instances

Signed-off-by: kay <kay.kim@10gen.com>
Branch: v3.4
https://github.com/mongodb/docs/commit/ee2e02d69f4bc42fecc7c00ccaf9d33ebaf42129

Comment by Githook User [ 30/Oct/17 ]

Author:

{'email': 'stennie@cpan.org', 'name': 'Stephen Steneker', 'username': 'stennie'}

Message: DOCS-5887: mongotop --locks is only supported for 2.6 and older instances

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/17bc281f055da55d3e7795f4cd8ebced80b23c0e

Generated at Thu Feb 08 07:51:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.