[DPE-2657] Fix replication after restore #273
Merged
Conversation
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
taurus-forever
approved these changes
Sep 29, 2023
Yes. The lag appears even on a demo installation due to the divergence in the timelines. |
dragomirp
approved these changes
Sep 30, 2023
This was referenced Feb 6, 2024
BON4
pushed a commit
to BON4/postgresql-k8s-operator
that referenced
this pull request
May 20, 2024
* Fix replication after restore * Fix words and format code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Issue
If we have a cluster of two or more units, scale it down to 1 unit, create a backup, restore the backup and scale up back again, the replication stop working due to reuse of the storage.
Solution
In that situation, as we see a huge replication lag, we need to reinitialise the replicas.
Fixes #262.