This repository was archived by the owner on May 1, 2025. It is now read-only.
DOCSP-47219 Midsync Reads FAQ #612
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. |
nvillahermosa-mdb
approved these changes
Feb 12, 2025
mvankeulen94
suggested changes
Feb 13, 2025
source/faq.txt
Outdated
|
|
||
| To learn more about permissable reads and writes during synchronization, see :ref:`c2c-reads-and-writes`. | ||
| ``mongosync`` combines and reorders writes from the source to destination during | ||
| synchronization, and temporarily modifies collection characteristics. As a |
There was a problem hiding this comment.
"combines and reorders writes" -> link to https://www.mongodb.com/docs/cluster-to-cluster-sync/current/reference/mongosync/mongosync-behavior/#consistency
"temporarily modifies" -> link to https://www.mongodb.com/docs/cluster-to-cluster-sync/current/reference/mongosync/mongosync-behavior/#temporary-changes-to-collection-characteristics
source/faq.txt
Outdated
| synchronization, and temporarily modifies collection characteristics. As a | ||
| result, ``mongosync`` can't guarantee that the destination matches the source, | ||
| including a stale version of the source, at any point in time when the sync is | ||
| running. To safely accept traffic to the destination cluster, wait for the |
There was a problem hiding this comment.
"running" -> "running, even if the sync is paused"
ajhuh-mdb
force-pushed
the
DOCSP-47219-midsync-reads-faq
branch
from
5579a4b to
233015c
Compare
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.9 v1.9
# Navigate to the new working tree
cd .worktrees/backport-v1.9
# Create a new branch
git switch --create backport-612-to-v1.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6149617fb5573b0ec01baa07274d2b6d0a2f2c26
# Push it to GitHub
git push --set-upstream origin backport-612-to-v1.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.9Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.8 v1.8
# Navigate to the new working tree
cd .worktrees/backport-v1.8
# Create a new branch
git switch --create backport-612-to-v1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6149617fb5573b0ec01baa07274d2b6d0a2f2c26
# Push it to GitHub
git push --set-upstream origin backport-612-to-v1.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.8Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.10 v1.10
# Navigate to the new working tree
cd .worktrees/backport-v1.10
# Create a new branch
git switch --create backport-612-to-v1.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6149617fb5573b0ec01baa07274d2b6d0a2f2c26
# Push it to GitHub
git push --set-upstream origin backport-612-to-v1.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.10Then, create a pull request where the |
github-actions bot
pushed a commit
that referenced
this pull request
Feb 13, 2025
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback (cherry picked from commit 6149617)
ajhuh-mdb
added a commit
that referenced
this pull request
Feb 13, 2025
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback (cherry picked from commit 6149617) Co-authored-by: Alison Huh <[email protected]>
ajhuh-mdb
added a commit
to ajhuh-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Feb 13, 2025
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback
ajhuh-mdb
added a commit
to ajhuh-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Feb 13, 2025
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback
ajhuh-mdb
added a commit
to ajhuh-mdb/docs-cluster-to-cluster-sync
that referenced
this pull request
Feb 13, 2025
* DOCSP-47219-midsync-reads * active voice * internal feedback * MVK feedback
ajhuh-mdb
added a commit
that referenced
this pull request
Feb 13, 2025
ajhuh-mdb
added a commit
that referenced
this pull request
Feb 13, 2025
ajhuh-mdb
added a commit
that referenced
this pull request
Feb 13, 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
STAGING
https://deploy-preview-612--docs-cluster-to-cluster-sync.netlify.app/faq/#can-i-perform-reads-or-writes-to-my-destination-cluster-while-mongosync-is-syncing-
JIRA
https://jira.mongodb.org/browse/DOCSP-47219