Skip to content
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

check keyspace snapshot time for restore #105

Closed
wants to merge 10 commits into from

Conversation

pbibra
Copy link

@pbibra pbibra commented Jul 20, 2023

Description

Snapshot restores are no longer restoring from the backup before or at the snapshot time. Regression introduced here: vitessio#8824

This is breaking our PITR workflow. v14 is no longer supported upstream so adding the fix in our fork. Opened an issue and PR upstream, but in discussion about the eventual deprecation of snapshot keyspaces in favor of incremental backups/restores.

Testing

Before, PITR tablets always restoring to latest backup

After:

pbibra@tablet-iad-dev-pitrincd1234loadtest-80-00-fsmq:~$ cat /mnt/vitess/vttablet/log/vttablet.log | grep found
I0718 12:08:11.547793   30934 backup.go:256] Restore: No restore_in_progress file found, checking no existing data is present
I0718 12:08:11.913137   30934 backupengine.go:223] Restore: found backup loadtest/80- 2023-07-15.110009.us_east_1c-0173597869 to restore using the specified timestamp of '2023-07-15.150000'

Also modified the existing TestRestoreImpl to properly check for custom backup times.

Before:
Screenshot 2023-07-24 at 9 10 00 AM

After: CI passes

@pbibra pbibra requested a review from a team as a code owner July 20, 2023 00:30
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
Signed-off-by: Priya Bibra <[email protected]>
@github-actions
Copy link

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale label Aug 26, 2023
@pbibra pbibra removed the Stale label Aug 31, 2023
@pbibra pbibra closed this Aug 31, 2023
@pbibra pbibra deleted the pbibra-fix-snapshot-restore branch August 31, 2023 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant