DOCSP-48355-treat-non-known-cancellations-fatal #671
Conversation
✅ Deploy Preview for docs-cluster-to-cluster-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Hi @ajayvijayakumar123 , could you take a look at this PR for an external review, whenever you get a chance? Thank you! |
| ``mongosync`` is still able to complete the sync. In the case that a | ||
| sync does not complete, ``mongosync`` writes a fatal log entry. | ||
|
|
||
| ``mongosync`` only exits with an info level log when it sees a normal |
There was a problem hiding this comment.
Ah sorry, I didn't mean for REP-5495 to generate a downstream DOCSP ticket. I think we should just document REP-5495's changes on the release notes based on the google doc.
I don't think we should include this in our general docs because it exposes too much information about our logs. We say that our logs are not versioned and can change at any time here. I think we can close this ticket as won't do.
@zhenxuanjameszhang do you have thoughts on this?
There was a problem hiding this comment.
I think currently something is broken that if we select manual to add release notes, a DOCSP ticket will still be auto generated. I have noted that on the release process to improve.
I trust your judgement on this.
DESCRIPTION
Update
mongosyncdocs w/ known normal cancellations & fatal cancellations.STAGING
https://deploy-preview-671--docs-cluster-to-cluster-sync.netlify.app/reference/mongosync/mongosync-behavior/#resilience
JIRA
https://jira.mongodb.org/browse/DOCSP-48355
SELF-REVIEW CHECKLIST
See the taxonomy tagging instructions and this example PR
EXTERNAL REVIEW REQUIREMENTS
What's expected of an external reviewer?