-
Notifications
You must be signed in to change notification settings - Fork 35
DOCSP-41105 new About mongosync page #345
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
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.
This is looking good! I left a few suggestions and questions for your consideration.
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 is on a great track! I just left a few additional suggestions/questions. Feel free to reach out if you want to discuss anything! Thanks @sonderdonk-mdb !
indexes and resolves document conflicts. If write blocking is enabled, | ||
``mongosync`` turns write operations back on. |
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.
[suggestion] let's use active voice here
indexes and resolves document conflicts. If write blocking is enabled, | |
``mongosync`` turns write operations back on. | |
indexes and resolves document conflicts. If you enable write blocking, | |
``mongosync`` turns write operations back on. |
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 struggled with this because in most situations it is mongosync that enables write blocking, not the user (above I write "mongosync
halts any writes on the
source cluster"). What do you think about saying, "If write blocking is true
"?
* DOCS-41102 * DOCSP-41102 added to quickstart * DOCSP-41102
* DOCSP-40138-Mongosync-Delay-After-Resume-Restart * add 1.8 to toc * * * * * JA feedback * add retry bit
DESCRIPTION
Created an "About mongosync" page that details the C2C process from start to finish
I also added a sentence linking the "about mongosync" page on the index page and added a small note to the "mongosync states" page.
Note for reviewers: I have been debating the name for this page. I went with "About mongosync" but "How mongosync Works" has been suggested.
STAGING
About mongosync: https://preview-mongodbsonderdonkmdb.gatsbyjs.io/cluster-sync/DOCSP-41105/reference/about-mongosync/
Index page: https://preview-mongodbsonderdonkmdb.gatsbyjs.io/cluster-sync/DOCSP-41105/
mongosync States: https://preview-mongodbsonderdonkmdb.gatsbyjs.io/cluster-sync/DOCSP-41105/reference/mongosync-states/
JIRA
https://jira.mongodb.org/browse/DOCSP-41105
BUILD LOG
https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=66959072fb8bd13b842ae240
SELF-REVIEW CHECKLIST
See the taxonomy tagging instructions and this example PR
EXTERNAL REVIEW REQUIREMENTS
What's expected of an external reviewer?