-
Notifications
You must be signed in to change notification settings - Fork 39
DOCSP-46814-finalize-cutover-typo #568
Conversation
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Just have one clarification question!
source/reference/cutover-process.txt
Outdated
If ``/commit`` is called and the values are not near | ||
``0`` or if the verifier is not in the stream hashing | ||
phase, the cutover process might take a long a time. | ||
If you call ``/commit`` and the ``lagTimeSeconds`` fields are |
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.
Sorry I know this is a bit out of scope for this typo PR
Just for clarification, is this condition saying that the cutover process might take a long time either if:
- You call
/commit
and and thelagTimeSeconds
fields are not near 0 - You call
/commit
and the verifier is not in the stream hashing phase
OR
Is it saying that the cutover process might take a long time either if:
- You call
/commit
and and thelagTimeSeconds
fields are not near 0 - The verifier is not in the stream hashing phase
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.
the first option. the cutover process requires /commit to be called
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.
Thanks for this clarification @ajhuh-mdb and @ajayvijayakumar123 ! I removed the mention of /commit in this sentence to avoid redundancy and improve clarity.
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!
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
* DOCSP-46814-finalize-cutover-typo * DOCSP-46814 copy edit * DOCSP-46814 copy edit (cherry picked from commit ce4e39e)
💔 Some backports could not be created
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
DESCRIPTION
fixes typo on finalize cutover page
STAGING
https://deploy-preview-568--docs-cluster-to-cluster-sync.netlify.app/reference/cutover-process/#verify-the-status-of-mongosync.
JIRA
https://jira.mongodb.org/browse/DOCSP-46814
SELF-REVIEW CHECKLIST
See the taxonomy tagging instructions and this example PR
EXTERNAL REVIEW REQUIREMENTS
What's expected of an external reviewer?