Skip to content

Commit 1314e94

Browse files
authored
DOCSP-28763 FAQ for slow operations warnings (#119)
* DOCSP-28763 Adds slow operation FAQ entry * Adjusts text * Adjusts text * Adjusts text * Adjusts text * Fixes per Jeff Allen
1 parent e9d0af1 commit 1314e94

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

source/faq.txt

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,3 +107,20 @@ have more than 2 non-arbiter nodes and you must sync from a non-arbiter
107107
node. Use the source cluster's connection string to specify a
108108
:ref:`read preference <mongodb-uri>` for a non-arbiter, data-bearing
109109
node.
110+
111+
What if I see a Slow Operation Warning?
112+
---------------------------------------
113+
114+
Slow operation warnings can occur during the initial sync or the application
115+
of a change event when there is a slow read operation on the source cluster
116+
or a slow write operation on the destination cluster. The warning may
117+
indicate network congestion or resource strain on the source or destination
118+
cluster.
119+
120+
While these warnings do not indicate failures in themselves, slow operations
121+
can cause operation timeout errors in ``mongosync`` and migration failures.
122+
123+
If you see slow operation warnings, check CPU, memory, and network usage on the
124+
source and destination clusters. If the clusters are underprovisioned for your
125+
needs, consider upgrading the cluster hardware.
126+

0 commit comments

Comments
 (0)