-
Notifications
You must be signed in to change notification settings - Fork 38
DOCSP-48421-clarify-verifier-lag-time #673
DOCSP-48421-clarify-verifier-lag-time #673
Conversation
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @autarch , could you take a look at this PR for a review, whenever you get a chance? Thanks! |
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 think this need a further clarification.
With the introduction of the :ref:`embdedded verfier<c2c-embedded-verifier>` | ||
in version 1.9, there are now three different ``lagTimeSeconds`` fields: | ||
- ``lagTimeSeconds`` for ``mongosync`` | ||
- ``lagTimeSeconds`` for the source cluster for the verifier | ||
- ``lagTimeSeconds`` for the destination cluster for the verifier |
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.
We should probably specify that there are 3 fields when embedded verification is enabled. Otherwise, there's just one.
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 @autarch , update made! Back to you.
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.
rendering issue
embedded verification is enabled: | ||
- ``lagTimeSeconds`` for ``mongosync`` | ||
- ``lagTimeSeconds`` for the source cluster for the verifier | ||
- ``lagTimeSeconds`` for the destination cluster for the verifier |
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 not rendering right in the table
Thanks @gmiller-mdb ! Back to you! |
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-48421-clarify-verifier-lag-time * build error * reviewer update * fix render (cherry picked from commit 3fb8e0b)
* DOCSP-48421-clarify-verifier-lag-time * build error * reviewer update * fix render (cherry picked from commit 3fb8e0b)
* DOCSP-48421-clarify-verifier-lag-time * build error * reviewer update * fix render (cherry picked from commit 3fb8e0b)
* DOCSP-48421-clarify-verifier-lag-time * build error * reviewer update * fix render (cherry picked from commit 3fb8e0b)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
DESCRIPTION
Clarifies that there are 3 diff
lagTimeSeconds
fields in theprogress
response in the progress page & commit page.STAGING
JIRA
https://jira.mongodb.org/browse/DOCSP-48421
SELF-REVIEW CHECKLIST
See the taxonomy tagging instructions and this example PR
EXTERNAL REVIEW REQUIREMENTS
What's expected of an external reviewer?