Skip to content
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

Open
wants to merge 3 commits into
base: v1.8
Choose a base branch
from

Conversation

ltran-mdb2
Copy link
Collaborator

@ltran-mdb2 ltran-mdb2 commented Apr 9, 2024

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

  • Does each file have 3-5 taxonomy facet tags?
    See the taxonomy tagging instructions and this example PR
  • Is this free of any warnings or errors in the RST?
  • Is this free of spelling errors?
  • Is this free of grammatical errors?
  • Is this free of staging / rendering issues?
  • Are all the links working?

EXTERNAL REVIEW REQUIREMENTS

What's expected of an external reviewer?

Copy link
Collaborator

@jeff-allen-mongo jeff-allen-mongo left a 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!

specify a read preference, ``mongosync`` uses the read preference
:readmode:`primaryPreferred` on the source cluster.

By default, ``mongosync`` uses the read preference :readmode:`primary`
Copy link
Collaborator

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Copy link
Collaborator

@kauboy26 kauboy26 left a 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.

Copy link
Collaborator

@edobranov edobranov left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants