Release 2.8.0 #1068
Merged
Release 2.8.0 #1068
Conversation
This file contains 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
PBM's multiple endpoint feature enables possibility to specify different endpoint urls for the different cluster members. Supported storage types are: S3 and Azure.
* Add restore's ns-from and ns-to options They are used for cloning existing collection from the backup (--ns-from) into the new collection with the different name (--ns-to). * Expand restore cmd with nsFrom/To * Pass nsFrom/To options to mongorestore * Fine tune mongorestore to support coll cloning. Following settings are applied: mongorestore has additional options: ns include for target collection; preserved UUID and dropping collections should be turned off for cloning collection. pbm restore should be run in selective mode, and selected ns should be cloning collection * Add tests for resolving ns and users&userAndRoles when cloning collections * Add CLI validation for --ns-from and --ns-to opts * Check whether the target cloning collection exists * Add index cloning support * Extract cloning to/from into separate type * Add tests for cloning validation * Add guard for cloning within sharded cluster Cloning feature is not supported in sharded cluster in this version. * Fix reviewdog warnings * Disable oplog apply when cloning collection * Add validation for incomplete ns
… from config file
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
fix formatting and add a default value to help Co-authored-by: Dmytro Zghoba <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
PKG-262 hetzner: retry downloading GO binary for 3 times
… until 8.0 release (#1047)
* Remove guard for cloning ns with PITR * Expand oplog options with cloning namespace * Add logic for getting UUID from namespace * Add oplog entries cloning functionality * Add guard for backup without source cloning collections * Fix transaction handling for cloning namespace
Update README.md
PBM-1444: Cloning for create/drop ops
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
CI. Upload results to codecov, add possibility to build PBM with coverage profiling
…kers-fix PBM-1414 fix reading the NumParallelCollections configuration
…kers-value-to-10 PBM-1414 revert the default for numInsertionWorkers to 10
PKG-251 add AL2023
Ensure that oplog is applied on Primary node during Physical Restore When applying oplog chunks on the the Primary node, it might happen that Primary node is still not reached Primary state, simply because after its restart, it is in transition towards Primary: STARTUP -> STARTUP2 -> RECOVERING -> SECONDARY -> PRIMARY To fix such a situation, PBM checks if the Primary state is reached. After the Primay state is reached, oplog is applied on that Primary.
…option is specified (#1066) Apply logger opts when db conn still doesn't exist.
…h name remapping (#1063) Fix indexes cloning logic to support drop op: During drop operation within oplog, indexes catalog is modified with cloning-to ns. Therefore it is necessary to have modified index catalog (with cloned collection) before we start applying the oplog. The approach to modify index catalog with cloning collection during the snapshot restore phase, ensures that PITR restore will be correctly applied also on index catalog.
sandraromanchenko
requested review from
defbin and
boris-ilijic
as code owners
boris-ilijic
previously approved these changes
Dec 9, 2024
boris-ilijic
approved these changes
Dec 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.