mongosync enters different states depending on the requests it
mongosync can only be in a single state at a given time.
mongosync states determines which API operations you can
This page describes
The following table describes each state and lists the permitted operations in that state.
Possible API Operations
The sync process is currently running. In this state, data is initially synced to the destination cluster. Subsequent writes to the source cluster are applied to the destination cluster.
The sync process is paused. To resume the sync process, send a request to the /resume endpoint.
The cutover for the sync process has started. The time it takes to transition to the
The cutover for the sync process is complete.
Read operations on the source cluster are always permitted.
/progress endpoint reports
data on the source and destination clusters is consistent.
To see what state
mongosync is in, call the /progress API endpoint. The
/progress output includes a
true, it is safe to write to the destination cluster.
false, do not write to the destination cluster.
You can safely write to the source cluster while
syncing. Do not write to the destination cluster unless
When write-blocking is enabled,
mongosync blocks writes:
On the destination cluster during sync
On the source cluster while committing
To enable write-blocking, use the start API
true. You cannot enable
write-blocking after the sync starts.
enableUserWriteBlocking, writes are only blocked for users
that do not have the
bypassWriteBlockingMode ActionType. Users
who have this ActionType are able to perform writes.