DOCSP-1504: list operations that are not causally consistent

Author: kay-kim

source/core/read-isolation-consistency-recency.txt

@@ -200,3 +200,57 @@ Operations can be causally consistent across different sessions.
    operation time of one client session to be consistent with the operations
    of another client session.
 
+.. _causal-consistency-limitations:
+
+Limitations
+~~~~~~~~~~~
+
+The folowing operations that build in-memory structures are not
+causally consistent:
+
+.. list-table::
+   :header-rows: 1
+
+   * - Operation
+     - Notes
+
+   * - :dbcommand:`collStats`
+
+     - 
+
+   * - :pipeline:`$collStats` with ``latencyStats`` option.
+
+     - 
+
+   * - :pipeline:`$currentOp`
+
+     - Returns an error if the operation is associated with a causally
+       consistent client session.
+
+   * - :dbcommand:`dbStats`
+
+     - 
+
+   * - :dbcommand:`getMore`
+
+     - Returns an error if the operation is associated with a causally
+       consistent client session.
+
+   * - :pipeline:`$indexStats`
+
+     - 
+
+   * - :dbcommand:`ping`
+
+     - Returns an error if the operation is associated with a causally
+       consistent client session.
+
+   * - :dbcommand:`serverStatus`
+
+     - Returns an error if the operation is associated with a causally
+       consistent client session.
+
+   * - :dbcommand:`createIndex` with ``background: true`` option; i.e.
+       background index builds
+
+     - 

source/release-notes/3.6.txt

@@ -727,6 +727,11 @@ Known Issues in 3.6.0
 - :issue:`WT-3724`:
       .. include:: /includes/3.6-osx-platform.rst
 
+- Operations that build in-memory structures are not causally
+  consistent; however, only some operations return errors when
+  associated with causally consistent sessions. See :ref:`Causal
+  Consistency Limitations <causal-consistency-limitations>`.
+
 .. seealso::
 
    `All JIRA issues resolved in 3.6 <http://bit.ly/2jJFa85>`_.