Release 2.7.0 #1031
Open
Release 2.7.0 #1031
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
* PKG-157 pbm: add marketing message to postinstall --------- Co-authored-by: Oleksandr Miroshnychenko <[email protected]>
…1005) * Add restore start and finish time info * Fix help text for oplog-replay command * Remove StartPITR info from describe-restore cmd * Add finish time only for successful restore
* Fix priority status for Delayed member * Fix priority calculation for Delayed member
* Fix endless loop when writing cluster last_write_ts * Increase polling time when writing last_write_ts on the cluster level * Add optimization to fetch all locks at ones
…eated during oplog slicing (#1012) * Enable using recreated UUID with TimeSeries view: PBM recreates UUID for the time series collection. This fix uses the same recreated UUID when adding the view for the time series collection.
This change allows to retrieve credentials from ECS and EKS roles.
the leader only sets the status. no reason to wait for known condition
backup status can be set to done in db meta before the meta is written to storage. if the write fails, no meta will be available on storage. storage resync will delete backup meta from db and won't see it on storage.
…1019) * Fix inconsistent data after physical restore with PITR After PITR physical restore, there was inconsistent data between Primary and Secondaries nodes. The reason was that PITR oplog and dropping collections are applied in reverse order: - on Primary: [PITR oplog apply] -> [dropping PBM databases] - on each Secondary: [dropping PBM databases] -> [catch up from Primary including oplog apply] Not using DDL operations (drop in this case) for PBM's system collections fixes the problem. * Expand setupNewDB logic with all PBM's collections That ensures that collection will not be created during PITR and by doing that we eliminate the possible problem of having different UUIDs.
to force agent status cleanup
defbin
requested review from
sandraromanchenko,
olexandr-havryliak and
radoslawszulgo
boris-ilijic
previously approved these changes
Oct 2, 2024
boris-ilijic
approved these changes
Oct 3, 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.