This repository was archived by the owner on May 1, 2025. It is now read-only.
DOCSP-48525-disaster-recovery-faq-entry #679
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
gmiller-mdb
approved these changes
Mar 18, 2025
source/faq.txt
Outdated
|
|
||
| No, you can't currently set up a Disaster Recovery cluster with ``mongosync``, | ||
| since ``mongosync`` must commit in order to safely accept traffic to the |
There was a problem hiding this comment.
[s] Do you want to add the bold to 'must commit' here like in the ticket?
mvankeulen94
suggested changes
Mar 19, 2025
| @@ -23,6 +23,8 @@ Can I change the load level while ``mongosync`` is syncing? | |||
| Yes, you can adjust the cluster workload level during a migration by | |||
| following the steps in :ref:`c2c-reconfigure-mid-migration`. | |||
|
|
|||
| .. _c2c-faq-reads-writes-mongosync: | |||
|
|
|||
| Can I perform reads or writes to my destination cluster while ``mongosync`` is syncing? | |||
There was a problem hiding this comment.
can we add this as the question right under "Can I perform reads or writes to my destination cluster while mongosync is syncing?" ?
source/faq.txt
Outdated
| efficiently across the destination cluster’s shards after migration. | ||
|
|
||
| Can I use ``mongosync`` to set up a Disaster Recovery cluster? |
There was a problem hiding this comment.
on second thought, it's better to say "maintain" instead of "set up" here, since the key issue is the lack of an ability to keep the cluster up to date with the source
source/faq.txt
Outdated
| -------------------------------------------------------------- | ||
|
|
||
| No, you can't currently set up a Disaster Recovery cluster with ``mongosync``, |
source/faq.txt
Outdated
|
|
||
| No, you can't currently set up a Disaster Recovery cluster with ``mongosync``, | ||
| since ``mongosync`` **must commit** in order to safely accept traffic to the |
There was a problem hiding this comment.
| @@ -0,0 +1,4 @@ | |||
| Until you've called commit on ``mongosync`` and ``canWrite`` successfully | |||
There was a problem hiding this comment.
| @@ -219,6 +219,10 @@ For any continuous synchronization use cases with ``mongosync``, ensure that | |||
| ``mongosync`` commits before cutting over from the source to the | |||
There was a problem hiding this comment.
this line starting with "For any continuous synchronization" is now redundant with the new textbox so we can remove it.
|
Thank you for your review @mvankeulen94 ! Back to you with the updates. |
amalhotra-mdb
added a commit
to amalhotra-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Mar 24, 2025
* DOCSP-48525-disaster-recovery-faq-entry * wording * build error * reviewer request * add important * monospace * reviewer updates * render issue (cherry picked from commit 9036320)
amalhotra-mdb
added a commit
to amalhotra-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Mar 24, 2025
* DOCSP-48525-disaster-recovery-faq-entry * wording * build error * reviewer request * add important * monospace * reviewer updates * render issue (cherry picked from commit 9036320)
amalhotra-mdb
added a commit
to amalhotra-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Mar 24, 2025
* DOCSP-48525-disaster-recovery-faq-entry * wording * build error * reviewer request * add important * monospace * reviewer updates * render issue (cherry picked from commit 9036320)
amalhotra-mdb
added a commit
to amalhotra-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Mar 24, 2025
* DOCSP-48525-disaster-recovery-faq-entry * wording * build error * reviewer request * add important * monospace * reviewer updates * render issue (cherry picked from commit 9036320)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
amalhotra-mdb
added a commit
that referenced
this pull request
Mar 24, 2025
amalhotra-mdb
added a commit
that referenced
this pull request
Mar 24, 2025
amalhotra-mdb
added a commit
that referenced
this pull request
Mar 24, 2025
amalhotra-mdb
added a commit
that referenced
this pull request
Mar 24, 2025
amalhotra-mdb
added a commit
to amalhotra-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Mar 25, 2025
* DOCSP-48525-disaster-recovery-faq-entry * wording * build error * reviewer request * add important * monospace * reviewer updates * render issue
amalhotra-mdb
added a commit
that referenced
this pull request
Mar 25, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIPTION
Add question to C2C FAQ ab using mongosync for disaster recovery.
STAGING
JIRA
https://jira.mongodb.org/browse/DOCSP-48525
BUILD LOG
Self-Review Checklist
External Review Requirements
What's expected of an external reviewer?