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]: DDLs failing on DB2 after restore is done on DB1 #13505

Open
Karvy-yb opened this issue Aug 2, 2022 · 0 comments
Open

[DocDB] [PITR]: DDLs failing on DB2 after restore is done on DB1 #13505

Karvy-yb opened this issue Aug 2, 2022 · 0 comments
Assignees
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue
Projects

Comments

@Karvy-yb
Copy link

Karvy-yb commented Aug 2, 2022

Jira Link: DB-3101

Description

Steps followed:

  1. Create new database (say DB1)
  2. Create snapshot schedule for DB1
  3. Note the timestamp
  4. Run multiple alter commands on DB2
  5. Simultaneously do a restore for DB1 to time in point#3

Restore takes longer than usual and post restore one of the alter operation fails following which all of the upcoming start throwing unexpected error.
So, there are couple of issues here:

  1. Operation on DB2 failing because of restore on DB1
  2. Even if one operation fails the following alter operations should not error out except one. As I am altering to add column to the table and dropping that column in a pair, only one operation should error because of failure. After which Alter should be working fine.

Finally after the script ends, I am unable to query read for the particular table. It errors out saying ERROR: Invalid argument: Invalid column number 29

This is a reproducible issue and I am attaching the SS of the outputs as well as the log files of around the time.

Screenshot 2022-08-01 at 5 46 34 PM

Screenshot 2022-08-01 at 5 46 23 PM

master_logs_0523.txt

master_logs_0522.txt

tserver_logs_0522.txt

tserver_logs_0523.txt

.

@Karvy-yb Karvy-yb added area/docdb YugabyteDB core features status/awaiting-triage Issue awaiting triage labels Aug 2, 2022
@Karvy-yb Karvy-yb added this to To do in PITR via automation Aug 2, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Aug 2, 2022
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Aug 9, 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/bug This issue is a bug priority/medium Medium priority issue
Projects
PITR
To do
Development

No branches or pull requests

4 participants