Skip to content

Commit fef9969

Browse files
DOCSP-38696 Add faq regarding fatal errors (#305)
* DOCSP-38696 add faq * DOCSP-38696 jason feedback
1 parent ce6c77d commit fef9969

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

source/faq.txt

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,6 +136,14 @@ These logs do not indicate that ``mongosync`` is failing or corrupting
136136
data. If a fatal error occurs, ``mongosync`` stops the sync and writes a
137137
fatal log entry.
138138

139+
What should I do if mongosync returns a fatal error?
140+
----------------------------------------------------
141+
142+
A fatal error indicates a problem that must be corrected and requires the
143+
migration to be restarted. After addressing the error, delete all migrated
144+
data on the destination cluster, including the ``mongosync_reserved_for_internal_use``
145+
database. Then, relaunch ``mongosync`` and start a new migration.
146+
139147
Does ``mongosync`` Support TTL Indexes?
140148
----------------------------------------
141149

0 commit comments

Comments
 (0)