-
Notifications
You must be signed in to change notification settings - Fork 2
PCSM-256 Release notes 0.7.0 #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
016d7cf
2f5666c
1cfb84c
2b3af30
17bfc61
51e4975
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| # {{ pcsm.full_name }} 0.7.0 ({{ date.v0_7_0 }}) | ||
|
Check warning on line 1 in docs/release-notes/0.7.0.md
|
||
|
|
||
| We are excited to announce the general availability (GA) of {{ pcsm.full_name }} ({{pcsm.short}}) for data replication across replica sets. The GA status means {{ pcsm.short }} has passed the stability and reliability milestones required for enterprise use. You can confidently deploy it in production for data migration across replica sets with near-zero downtime. | ||
|
Check warning on line 3 in docs/release-notes/0.7.0.md
|
||
|
|
||
| This release also introduces data replication in sharded clusters in a tech preview stage. While not yet GA, this feature is available for testing. We encourage you to try it in non‑production environments and share feedback to help shape future improvements. | ||
|
Check warning on line 5 in docs/release-notes/0.7.0.md
|
||
|
|
||
| [Get started with {{pcsm.short}}](../installation.md){.md-button} | ||
|
|
||
| ## Release highlights | ||
|
|
||
| This release provides the following new features and improvements: | ||
|
|
||
| ### Data replication in sharded clusters | ||
|
|
||
| You can now replicate data between sharded MongoDB clusters or sync data from one sharded deployment to another. This makes it easier to migrate clusters with minimal downtime, set up disaster recovery across sharded environments, or keep data in sync for testing and development. | ||
|
|
||
| {{pcsm.short}} connects to `mongos` in both the source and target sharded clusters. This means clusters can have different numbers of shards, and you don't need to disable the balancer. Note that {{pcsm.short}} replicates data only, not metadata. That means chunk distribution and the primary shard for a collection may look different between your source and target clusters. | ||
|
Check warning on line 17 in docs/release-notes/0.7.0.md
|
||
|
|
||
| This feature is in the tech preview stage. We don't recommend using it in production yet, but we encourage you to try it in testing or staging environments and share your feedback. Your input will help us improve and shape the future of {{pcsm.full_name}}. | ||
|
Check warning on line 19 in docs/release-notes/0.7.0.md
|
||
|
|
||
| Learn more about sharding support in our [documentation](../sharding.md) | ||
|
Check warning on line 21 in docs/release-notes/0.7.0.md
|
||
|
|
||
| ### New deployment options | ||
|
|
||
| In addition to installing {{pcsm.full_name}} from repositories or building from source, you now have two new options: | ||
|
|
||
| * **Run {{pcsm.short}} in Docker** – quickly spin up a containerized environment with consistent dependencies and easy portability. | ||
|
Check failure on line 27 in docs/release-notes/0.7.0.md
|
||
| * **Install from binary tarballs** – drop in pre-built binaries for fast setup, even in environments without package managers or container runtimes. | ||
|
Check failure on line 28 in docs/release-notes/0.7.0.md
|
||
|
|
||
| These new deployment methods give you more flexibility to choose the approach that best fits your infrastructure, whether you're working in cloud-native setups, air‑gapped systems, or lightweight test environments. | ||
|
|
||
| Refer to our [Quickstart guide](../installation.md) for detailed instructions on these new deployment options. | ||
|
Check warning on line 32 in docs/release-notes/0.7.0.md
|
||
|
|
||
| ### Fine-tune the timeout for MongoDB client operations | ||
|
|
||
| In smaller and medium‑sized clusters, the default MongoDB client operations timeout of 5 minutes is usually enough to complete data replication. However, in larger clusters, replication could fail if operations like insert, delete, or update take longer than this default limit. | ||
|
|
||
| You can now override the default timeout using the `PCSM_MONGODB_CLI_OPERATION_TIMEOUT` environment variable. This gives you control to extend the timeout when working with large datasets or complex replication tasks, ensuring replication continues smoothly without being interrupted by the 5‑minute limit. | ||
|
Check notice on line 38 in docs/release-notes/0.7.0.md
|
||
|
|
||
| Learn more about this and other available environment variables in our [documentation](../install/parameters.md). | ||
|
Check warning on line 40 in docs/release-notes/0.7.0.md
|
||
|
|
||
| ## Changelog | ||
|
|
||
| ### New Feature | ||
|
Check warning on line 44 in docs/release-notes/0.7.0.md
|
||
|
|
||
| * [PCSM-167](https://perconadev.atlassian.net/browse/PCSM-167) - Improved the status output to include the total number of events and display the time of the last replication operation in human-readable format | ||
|
Check notice on line 46 in docs/release-notes/0.7.0.md
|
||
| * [PCSM-195](https://perconadev.atlassian.net/browse/PCSM-195) - Added the ability to clone sharded collections | ||
|
Check notice on line 47 in docs/release-notes/0.7.0.md
|
||
| * [PCSM-207](https://perconadev.atlassian.net/browse/PCSM-207) - Expose MongoDB client operation timeout via env variable (Thank you user @balthazar for contributing to this issue) | ||
|
Check notice on line 48 in docs/release-notes/0.7.0.md
|
||
|
|
||
| ### Improvement | ||
|
|
||
| * [PCSM-238](https://perconadev.atlassian.net/browse/PCSM-238) - Finalization stage logs now include the namespace for each index | ||
|
Check notice on line 52 in docs/release-notes/0.7.0.md
|
||
|
|
||
| ### Bugs Fixed | ||
|
Check warning on line 54 in docs/release-notes/0.7.0.md
|
||
|
|
||
| * [PCSM-185](https://perconadev.atlassian.net/browse/PCSM-185) - Fixed a bug in the `pcsm status` command where `initialSync.lagTime` was incorrectly reported as non-zero value after the initial sync phase was finished. | ||
|
Check notice on line 56 in docs/release-notes/0.7.0.md
|
||
|
|
||
| * [PCSM-230](https://perconadev.atlassian.net/browse/PCSM-230) - Fixed the issue with incorrect handling of exclude and include filtered during the filtered sync. | ||
|
Check notice on line 58 in docs/release-notes/0.7.0.md
|
||
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.
https://perconadev.atlassian.net/browse/PCSM-167
Add to improvement section