Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,28 +11,29 @@

## Which MongoDB versions are supported?

- Source clusters: MongoDB 6.0.17 and later, including Atlas and MongoDB Enterprise editions.
- Source clusters: MongoDB 6.0.17 and later, including Atlas, MongoDB Enterprise Server, and Percona Server for MongoDB
- Target clusters: Percona Server for MongoDB 6.0.17 and later.

!!! 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.
PCSM supports MongoDB 6.0.17+, 7.0.13+, 8.0.0+, but the source and target must be on the same major version during sync.

Check notice on line 18 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L18

[Google.Acronyms] Spell out 'PCSM', if it's unfamiliar to the audience.
Raw output
{"message": "[Google.Acronyms] Spell out 'PCSM', if it's unfamiliar to the audience.", "location": {"path": "docs/faq.md", "range": {"start": {"line": 18, "column": 5}}}, "severity": "INFO"}

Check [Supported deployments](deployment.md) to learn more.

## Can I sync from Atlas to a self-hosted Percona Server for MongoDB?

Yes. {{pcsm.full_name}} is explicitly built to support Atlas to Percona Software migrations with minimal effort.
Yes. {{pcsm.full_name}} is explicitly built to support Atlas to Percona Server for MongoDB migrations with minimal effort.

## Does {{pcsm.full_name}} require a replica set on the source or target?

Yes. Both the source and target must be replica sets.

## Does {{pcsm.full_name}} support sharded clusters?

No. Sharded MongoDB clusters are not supported as either source or target at this time. Support for shard-to-shard replication is planned for a future release.
Yes. Sharded MongoDB clusters are supported as both sources and targets. Note: this feature is currently in technical preview. Support for shard-to-shard replication is planned for a future release.

Check notice on line 32 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L32

[Google.Passive] In general, use active voice instead of passive voice ('are supported').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are supported').", "location": {"path": "docs/faq.md", "range": {"start": {"line": 32, "column": 31}}}, "severity": "INFO"}

Check notice on line 32 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L32

[Google.Passive] In general, use active voice instead of passive voice ('is planned').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is planned').", "location": {"path": "docs/faq.md", "range": {"start": {"line": 32, "column": 167}}}, "severity": "INFO"}

## Does {{pcsm.full_name}} support bidirectional sync?

No. {{pcsm.full_name}} currently supports one-way synchronization only (source → target). However, you can re-run Percona {{pcsm.full_name}} with a reversed connection strings to do the other direction sync.
No. {{pcsm.full_name}} currently supports one-way synchronization only (source → target). However, you can rerun Percona {{pcsm.full_name}} with reversed connection strings to perform the other-direction sync.

Check notice on line 36 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L36

[Google.Parens] Use parentheses judiciously.
Raw output
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "docs/faq.md", "range": {"start": {"line": 36, "column": 72}}}, "severity": "INFO"}

## Is there a way to monitor sync progress?

Expand All @@ -50,6 +51,12 @@
- It uses checkpointing to resume from the last known sync point after a restart.
- Logs include detailed error reporting for troubleshooting.

## What database read and write concerns are used?

Check notice on line 54 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L54

[Google.Passive] In general, use active voice instead of passive voice ('are used').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are used').", "location": {"path": "docs/faq.md", "range": {"start": {"line": 54, "column": 42}}}, "severity": "INFO"}
By default, Percona ClusterSync for MongoDB uses the `"majority"` read concern level for reads on the source cluster. For writes to the destination cluster, the tool uses a write concern level of `"majority"` with `j: true`.




## What features are planned for future releases?

High availability, performance improvements, and shard-to-shard replication are the next features we are working on.
We're currently working on high availability with multiple PCSM instances and shard-to-shard replication.

Check warning on line 62 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L62

[Google.We] Try to avoid using first-person plural like 'We'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'We'.", "location": {"path": "docs/faq.md", "range": {"start": {"line": 62, "column": 2}}}, "severity": "WARNING"}

Check notice on line 62 in docs/faq.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/faq.md#L62

[Google.Acronyms] Spell out 'PCSM', if it's unfamiliar to the audience.
Raw output
{"message": "[Google.Acronyms] Spell out 'PCSM', if it's unfamiliar to the audience.", "location": {"path": "docs/faq.md", "range": {"start": {"line": 62, "column": 61}}}, "severity": "INFO"}
Loading