Skip to content

Commit 7967ebd

Browse files
jason-price-mongodbjeff-allen-mongo
authored andcommitted
DOCS-13613 log time spent waiting for other shards
1 parent 098527d commit 7967ebd

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

source/reference/log-messages.txt

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,38 @@ a slow :doc:`aggregation </aggregation>` operation:
5656

5757
2019-01-14T12:00:59.166-0500 I COMMAND [conn4] command test.items appName: "MongoDB Shell" command: aggregate { aggregate: "items", pipeline: [ { $match: { a: { $lte: 500.0 } } }, { $sort: { a: -1.0 } } ], allowDiskUse: true, cursor: {}, lsid: { id: UUID("a73100a6-2f4d-48b7-a119-4632491c20eb") }, $db: "test" } planSummary: IXSCAN { a: 1, _id: -1 } cursorid:4808731480531288834 keysExamined:12524506 docsExamined:25003 hasSortStage:1 usedDisk:1 fromMultiPlanner:1 numYields:98113 nreturned:101 queryHash:811451DD planCacheKey:759981BA reslen:1305014 locks:{ Global: { acquireCount: { r: 98211, w: 98211 } }, Database: { acquireCount: { r: 98211 } }, Collection: { acquireCount: { r: 98211 } } } storage:{ data: { bytesRead: 112803842, timeReadingMicros: 62720 } } protocol:op_msg 39658ms
5858

59+
.. _log-messages-remoteOpWaitMillis:
60+
61+
Time Waiting for Shards Logged in ``remoteOpWaitMillis`` Field
62+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
63+
64+
.. versionadded:: 4.2.10
65+
66+
Starting in MongoDB 4.2.10, you can use the ``remoteOpWaitMillis`` log
67+
field to obtain the wait time (in milliseconds) for results from
68+
:term:`shards <shard>`.
69+
70+
``remoteOpWaitMillis`` is only logged:
71+
72+
- If you configure :ref:`slow operations logging
73+
<log-message-slow-ops>`.
74+
75+
- On the :term:`shard` or :binary:`~bin.mongos` that merges the results.
76+
77+
To determine if a merge operation or a shard issue is causing a slow
78+
query, compare the ``durationMillis`` and ``remoteOpWaitMillis`` time
79+
fields in the log. ``durationMillis`` is the total time the query took
80+
to complete. Specifically:
81+
82+
- If ``durationMillis`` is slightly longer than ``remoteOpWaitMillis``,
83+
then most of the time was spent waiting for a shard response. For
84+
example, ``durationMillis`` of 17 and ``remoteOpWaitMillis`` of 15.
85+
86+
- If ``durationMillis`` is significantly longer than
87+
``remoteOpWaitMillis``, then most of the time was spent performing the
88+
merge. For example, ``durationMillis`` of 100 and
89+
``remoteOpWaitMillis`` of 15.
90+
5991
Timestamp (Console/Log File)
6092
----------------------------
6193

0 commit comments

Comments
 (0)