DOCSP-12324 doc for killOp command (#76)

* DOCSP-12324 doc for killOp command

* DOCSP-12324 updates for copy review feedback

* DOCSP-12324 updates for tech review feedback

Author: kanchana-mongodb

source/admin/determine-query-status.txt

@@ -50,6 +50,11 @@ documents with the following fields:
      - string
      - Type of operation. Value is always ``op``. 
 
+   * - ``$currentOp.opid``
+     - :manual:`ObjectId </reference/bson-types/#objectid>`
+     - Unique identifier of the operation in :manual:`ObjectId 
+       </reference/bson-types/#objectid>` format. 
+
    * - ``$currentOp.client``
      - string
      - IP address (or hostname) and the ephemeral port of the client 
@@ -58,10 +63,10 @@ documents with the following fields:
    * - ``$currentOp.clientMetadata``
      - Document
      - Additional client information such as the client: 
-	   .. container::
-	      - Application name 
-	      - Driver name and version number
-	      - Operating System name, type, architecture, and version number
+
+       - Application name 
+       - Driver name and version 
+       - Operating system name, type, architecture, and version 
 
    * - ``$currentOp.active``
      - boolean
@@ -113,8 +118,8 @@ For the example below, suppose the following query is being run on the
 
    db.airbnb.find( { "address.market" : "Porto", "review_scores.review_scores_rating": {$gt: 79}})
 
-The following example returns information on the previous query being run on the 
-``airbnb`` collection in the ``sample`` database: 
+The following example returns information on the previous query running on 
+the ``airbnb`` collection in the ``sample`` database: 
 
 .. code-block:: json 
 
@@ -130,6 +135,7 @@ processed at the time that ``$currentOp`` was run.
 
    {
 	 "type" : "op",
+	 "opid" : ObjectId("1635fa35bf73f4320c6f99d0"),
 	 "client" : "73.231.201.205:62351",
 	 "clientMetadata" : {
 		"application" : {

source/admin/terminate-running-query.txt

@@ -0,0 +1,96 @@
+.. _terminate-running-query:
+
+=============================================
+Terminate a Running {+data-lake-short+} Query
+=============================================
+
+.. default-domain:: mongodb
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
+You can terminate long-running queries using the :manual:`killOp 
+</reference/command/killOp/>` command. For more information, see 
+:manual:`killOp </reference/command/killOp/>`. In {+adl+}: 
+
+- The ``op`` parameter value is an :manual:`ObjectId 
+  </reference/bson-types/#objectid>`. 
+- The ``comment`` parameter is not supported.
+
+Only the user who issued the query can terminate the query. To run 
+this command, use :manual:`db.runCommand()
+</reference/method/db.runCommand>`. You must run :manual:`killOp 
+</reference/command/killOp/>` against the ``admin`` database. 
+
+.. _adl-killop-syntax: 
+
+Syntax 
+------
+
+.. code-block:: json 
+
+   db.runCommand([{ "killOp": 1, "op":  ObjectId(<hexadecimal>) }])
+
+.. _adl-killop-options:
+
+Options 
+-------
+
+.. list-table:: 
+   :header-rows: 1
+   :widths: 15 15 60 10
+
+   * - Field
+     - Type
+     - Description
+     - Necessity
+
+   * - ``op``
+     - :manual:`ObjectId </reference/bson-types/#objectid>`
+     - Unique identifier, in :manual:`ObjectId 
+       </reference/bson-types/#objectid>` format, of the operation 
+       to terminate. You can use :ref:`$currentOp 
+       <determine-query-status>` to retrieve the ``opid`` of the 
+       operation to terminate.
+     - Required
+
+.. _adl-killop-output:
+
+Output 
+------
+
+:manual:`killOp </reference/command/killOp/>` returns the following 
+if it succeeds in marking the specified operation for termination:
+
+.. code-block:: 
+   :copyable: false
+
+   { "info" : "attempting to kill op", "ok" : 1 }
+
+Note that the output is the same whether or not the operation being 
+terminated is currently running. You can use :ref:`$currentOp 
+<determine-query-status>` to verify that the operation was terminated.
+
+.. _adl-killop-egs:
+
+Examples 
+--------
+
+For the example below, suppose a query with ``opid`` value of 
+``ObjectId("1635fad364c529820c6f9e76")`` is running. The following 
+command terminates this query.
+
+.. code-block:: json 
+
+   use admin 
+   db.runCommand({ "killOp": 1, "op": ObjectId("1635fad364c529820c6f9e76") })
+
+The previous command returns the following: 
+
+.. code-block:: json 
+   :copyable: false 
+
+   { "info" : "attempting to kill op", "ok" : 1 }

source/query/query-data-lake.txt

@@ -275,3 +275,4 @@ results.
 
       /admin/optimize-query-performance
       /admin/determine-query-status
+      /admin/terminate-running-query