DOCSP 33265 Resilience of mongosync (#201)

ltran-mdb2 · web-flow · commit eea942f5a524 · 2023-11-27T15:59:33.000-05:00
* DOCSP-33265 mongosync resilience * DOCSP-33265 mongosync resilience * DOCSP-33265 rephrasing * DOCSP-33265 rephrasing * DOCSP-33265 rephrasing * DOCSP-33625 copy edits * DOCSP-33625 copy edits * DOCSP-33625 copy edits * DOCSP-33625 copy edits * DOCSP-33265 tech edits * DOCSP-33265 tech edits * DOCSP-33265 tech edits
diff --git a/source/faq.txt b/source/faq.txt
@@ -115,3 +115,11 @@ If you see slow operation warnings, check CPU, memory, and network usage on the
 source and destination clusters.  If the clusters are underprovisioned for your
 needs, consider upgrading the cluster hardware.
 
+Should I stop a migration if the logs contain the word "error" or "failure"?
+--------------------------------------------------------------------------
+
+No, logs that contain the word "error" or "failure" show non-fatal
+errors and do not signal that you need to stop ``mongosync`` early.
+These logs do not indicate that ``mongosync`` is failing or corrupting
+data. If a fatal error occurs, ``mongosync`` stops the sync and writes a
+fatal log entry. 
diff --git a/source/reference/mongosync.txt b/source/reference/mongosync.txt
@@ -259,6 +259,16 @@ System Collections
 
 .. include:: /includes/collections/behavior-system-collections.rst
 
+Resilience
+~~~~~~~~~~
+
+``mongosync`` is resilient and able to handle non-fatal errors. Logs
+that contain the word "error" or "failure" do not indicate that
+``mongosync`` is failing or corrupting data. For example, if a network
+error occurs, the ``mongosync`` log may contain the word "error' but
+``mongosync`` is still able to complete the sync. In the case that a
+sync does not complete, ``mongosync`` writes a fatal log entry. 
+
 .. _c2c-mongosync-examples:
 
 Examples
