DOCSP-45861 Older Version Support Task Page #533
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.
Thanks for these updates, @ajhuh-mdb! This one LGTM mod a nit.
Thanks,
Joe
|
Hey @ajayvijayakumar123 👋 Whenever you get the chance, could you review this docs PR for the older version support page? TIA! |
| To learn more about supported server versions, see | ||
| :ref:`c2c-server-version-compatibility`. | ||
|
|
||
| Steps |
There was a problem hiding this comment.
I think we should recommend using mongomirror or mongodump / mongorestore if the user can't upgrade their source cluster to 4.4+ and destination cluster to 6.0+.
@mvankeulen94, you mentioned that we should recommend users to use unsupported older versions of mongodump and mongorestore to perform a skip-level upgrade on https://jira.mongodb.org/browse/DOCSP-41415 's comments. I'm not sure if we should publicly recommend using unsupported versions of dump/restore. Thoughts?
There was a problem hiding this comment.
Ah got it. Similar to what you mentioned, I wasn't sure if we wanted to recommend that in our docs since it seemed like more of a workaround rather than an official solution. Can wait for Maria's comments on this, but I'm leaning towards not recommending this and maybe having users defer to support/reaching out to receive this recommendation instead.
There was a problem hiding this comment.
Thanks all, agreed that we shouldn't publicly document using unsupported versions of dump+restore. In the meantime since my July comment, we have introduced some internal guidance around migration from EOL'd versions. We can leave the public guidance scoped to officially supported tooling
There was a problem hiding this comment.
Perfect, sounds good.
There was a problem hiding this comment.
@mvankeulen94 to confirm, we don't want to mention dump/restore or mongomirror on this page?
| Embedded Verifier | ||
| ~~~~~~~~~~~~~~~~~ | ||
|
|
||
| When you sync from a pre-6.0 source cluster, enable the |
There was a problem hiding this comment.
@ajayvijayakumar123 is this strictly necessary? Now that embedded verification is decoupled from the persistence project, there are still migrations that wouldn't be able to proceed with verification. Can we remove this embedded verifier section and just link to the verify data transfer docs instead?
There was a problem hiding this comment.
Yup that works. I just wanted us to recommend users to verify pre-6.0 migrations. Linking to the verify data transfer docs sounds good
DESCRIPTION
mongosyncon pre-6.0 clustersSTAGING
JIRA
https://jira.mongodb.org/browse/DOCSP-45861