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

[DocDB] [PITR] Allow restore to a point in time before an upgrade #13158

Open
vkulichenko opened this issue Jul 5, 2022 · 0 comments
Open

[DocDB] [PITR] Allow restore to a point in time before an upgrade #13158

vkulichenko opened this issue Jul 5, 2022 · 0 comments
Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@vkulichenko
Copy link
Contributor

vkulichenko commented Jul 5, 2022

Jira Link: DB-2846

Description

Currently, restore to a point in time before a run of ysql_upgrade is disallowed: #11846

ysql_upgrade is a required step for all YugabyteDB upgrades, which means that PITR timeline is nullified every time the user goes through an upgrade, even a minor one.

This is a significant limitation that needs to be addressed. We need to do more testing and allow such restores whenever possible.

@vkulichenko vkulichenko added area/docdb YugabyteDB core features status/awaiting-triage Issue awaiting triage labels Jul 5, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Jul 5, 2022
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Jul 5, 2022
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature and removed kind/bug This issue is a bug labels Jul 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

2 participants