-
-
Notifications
You must be signed in to change notification settings - Fork 433
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
pgBackRest: Point-In-Time Recovery (PITR) Improvements #765
Merged
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
Add patroni_cluster_restore_timeout variable
vitabaks
changed the title
Add cluster restore timeout
Add cluster restore timeout and Standby cluster initialization check
Sep 20, 2024
vitabaks
changed the title
Add cluster restore timeout and Standby cluster initialization check
Add restore timeout and Standby Cluster initialization check
Sep 20, 2024
Rename patroni_cluster_restore_timeout to cluster_restore_timeout to make the variable shorter.
vitabaks
changed the title
Add restore timeout and Standby Cluster initialization check
pgBackRest: Point-In-Time Recovery (PITR) Improvements
Nov 1, 2024
TestResult:
|
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.
This PR introduces a configurable
cluster_restore_timeout
variable to replace hardcoded values and provide flexibility. The timeout has been increased to 24 hours, making it more suitable for restoring large databases, including both backup and WAL recovery.Additionally, we've added the task "Wait for the Standby cluster initialization to complete". This task allows tracking the progress of Standby cluster initialization in the Ansible logs. The same 24-hour timeout is applied to this task to ensure it has ample time to complete for large databases.
Variables:
cluster_restore_timeout
- backup and WAL restore timeout in seconds, default: 86400 (24 hours)pg_ctl_timeout
- pg_ctl start and stop timeout, default: 3600 (1 hour)Additionally
pgbackrest_patroni_cluster_restore_command
variable.--config-file
option.restore_command
option yo be able to restore WAL from the archive even if the postgresql_restore_command variable is not set.archive_command
option to eliminate the risk of archiving WAL immediately after the promotion. It makes sense for cloning when we don't want to send the WAL to the main cluster storage.