[DOCS-9425] Missing command information for fsyncUnlock command from Database Commands Created: 01/Dec/16  Updated: 30/Oct/23  Resolved: 17/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Christian Amor Kvalheim Assignee: Ravind Kumar (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-8007 Document currentOp command for 3.2+ Closed
related to SERVER-7775 Make special commands (inprog, killop... Closed
is related to DOCS-7106 Document the "killOp" command Closed
Participants:
Days since reply: 46 weeks, 6 days ago

 Description   

The information about the fsyncUnlock command is missing from the documentation.

https://docs.mongodb.com/v3.2/reference/command/



 Comments   
Comment by Sarah Olson [ 17/Mar/23 ]

Closing this out on the grounds that:

  • Details of this request are significantly outdated. 
  • Our documentation has evolved substantially since this request was made. 

Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree.

Comment by Ravind Kumar (Inactive) [ 01/Dec/16 ]

Ah, got it. Thanks rassi

Note, commit + line # here

Comment by J Rassi [ 01/Dec/16 ]

db.fsyncLock() is implemented with the "lock" option to the fsync command (introduced in 1.4). See https://docs.mongodb.com/manual/reference/command/fsync/#dbcmd.fsync.

Before version 3.2:

  • db.fsyncUnlock() is implemented with a query on the "db.$cmd.sys.unlock" namespace.
  • db.killOp() is implemented with a query on the "db.$cmd.sys.killop" namespace.
  • db.currentOp() is implemented with a query on the "db.$cmd.sys.inprog" namespace.

The "fsyncUnlock", "killOp", and "currentOp" commands were introduced in server version 3.2 (SERVER-7775). In the 3.2 shell and later, the above three shell methods use these three new server commands (if the server connected to by the shell supports them).

The "killOp" command was documented in DOCS-7106, but the "fsyncUnlock" and "currentOp" commands still need documentation. See linked DOCS tickets.

Comment by Ravind Kumar (Inactive) [ 01/Dec/16 ]

I think the fsync dbcommand provides both lock and unlock capabilities.

Rather, there are database shell methods for fsynclock and fsyncunlock.

Is there also a dbcommand version of fsynclock and fsyncunlock? I don't see a DOCS ticket about either of them as far as dbcommands go. I do see SERVER-4760 but its not immediately clear if that resulted in the relevant commands being created.

kay.kim, can you verify?

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