Open
Conversation
rasika-chivate
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This PR resolves a documentation contradiction about PCSM supporting data migration “when upgrading to a new MongoDB version” while the product only supports synchronization within the same MongoDB major version.
Changes:
- Removes the “upgrading to a new MongoDB version” claim from the “Data migration” use case on the docs landing page.
- Adds a clarification note in the FAQ that source and target must be on the same major version during sync.
- Emphasizes “same major versions only” in the deployment version requirements section.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/index.md | Removes wording that implied cross-version upgrades during sync. |
| docs/faq.md | Adds a note clarifying same-major-version requirement during sync. |
| docs/deployment.md | Reinforces same-major-version-only synchronization requirement. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+17
to
+18
| !!! note | ||
| PCSM supports MongoDB 6.0.17+, 7.0.13+, 8.0.0+ but source and target must be on the same major version during sync. |
There was a problem hiding this comment.
The admonition is indented by 4 spaces here, which will typically make it render as a code block instead of a MkDocs/Material note. Align !!! note to the left margin (and keep the following content indented) so the admonition is parsed correctly.
Suggested change
| !!! note | |
| PCSM supports MongoDB 6.0.17+, 7.0.13+, 8.0.0+ but source and target must be on the same major version during sync. | |
| !!! note | |
| PCSM supports MongoDB 6.0.17+, 7.0.13+, 8.0.0+ but source and target must be on the same major version during sync. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix the contradiction in the PCSM documentation.
https://docs.percona.com/percona-clustersync-for-mongodb/index.html#why-you-need-pcsm
• Data migration:
PCSM simplifies the process of migrating data between clusters, whether you’re upgrading to a new MongoDB version, moving to a different vendor, or transitioning from cloud to on-premises.
But then...
https://docs.percona.com/percona-clustersync-for-mongodb/deployment.html#version-requirements
Version requirements
You can synchronize Percona Server for MongoDB or MongoDB Community/Enterprise Advanced/Atlas within the same major versions - 6.0 to 6.0, 7.0 to 7.0, 8.0 to 8.0.