-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOCS-15441 mongosync read preference behavior #298
base: v1.8
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM % a small suggestion. Thanks @ltran-mdb2!
source/reference/mongosync.txt
Outdated
specify a read preference, ``mongosync`` uses the read preference | ||
:readmode:`primaryPreferred` on the source cluster. | ||
|
||
By default, ``mongosync`` uses the read preference :readmode:`primary` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove "By default" here, because this kind of makes it read like users can modify the behavior.
Maybe we can say:
mongosync
always uses the :readmode:primary
read preference on the destination cluster, even if you manually specify a read preference for the destination cluster
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Let's get another reviewer from the mongosync team to double check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually doesn't apply anymore with the recent 1.7.2 release (you should get a merge conflict if you rebase onto master): f25a642#diff-a61a44aa44c4308e9fcfa894effe294e608468bf2a1e3cf752da6b039ef5f2beR274-R279
We can close out this ticket as Won't Do.
DESCRIPTION
On the source, mongosync uses the user specified read preference and uses the read preference PrimaryPreferred if they did not set any preference.
On the destination, mongosync overwrites the user specified read preference with Primary.
STAGING
https://preview-mongodbltranmdb2.gatsbyjs.io/cluster-sync/DOCS-15441/reference/mongosync/#read-preference
JIRA
https://jira.mongodb.org/browse/DOCS-15441
BUILD LOG
https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=6615857d3a5920a291966d88
SELF-REVIEW CHECKLIST
See the taxonomy tagging instructions and this example PR
EXTERNAL REVIEW REQUIREMENTS
What's expected of an external reviewer?