-
Type: New Feature
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Previously killOp, currentOp, and fsyncUnlock were implemented as queries on special system collections.
There are all being re-implemented as normal commands, with names taken from the corresponding shell helpers.
The name of command for the old "$cmd.sys.killop" system collection will be "killOp". As before it will have an "op" parameter indicating the operation that is being killed.
The name of the command for the old "$cmd.sys.unlock" system collection will be "fsyncUnlock" (to match fsyncLock).
The name of the command for the old "$cmd.sys.inprog" system collection will be "currentOp".
The behavior of the actual commands will be nearly unchanged - except for slightly improved error handling for incorrect parameter types.
UPDATE: there is a minor behavior change in currentOp/inprog - the currentOp operation itself will now appear in the "inprog" array of returned operations (similar to 'ps' on unix systems).
The server will deprecate the system collections in MongoDB 3.2.x. We anticipate that they will be removed in subsequent releases.
- depends on
-
CDRIVER-888 Make special commands (inprog, killop, unlock) go through the standard command codepath
- Closed
-
CXX-683 Make special commands (inprog, killop, unlock) go through the standard command codepath
- Closed
-
CXX-684 Make special commands (inprog, killop, unlock) go through the standard command codepath
- Closed
-
JAVA-1719 Re-implement Mongo.unlock and Mongo.isLocked with new database commands
- Closed
-
PHPLIB-126 Make special commands (inprog, killop, unlock) go through the standard command codepath
- Closed
-
PYTHON-979 Use fsyncUnlock and currentOp commands with MongoDB 3.2+
- Closed
-
RUST-22 Make special commands (inprog, killop, unlock) go through the standard command codepath
- Closed
-
CSHARP-1362 Support new Find server commands
- Closed
-
SERVER-7775 Make special commands (inprog, killop, unlock) go through the standard command codepath
- Closed