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

[backup] Restore lost some amount of values #13451

Closed
pilshchikov opened this issue Jul 27, 2022 · 3 comments
Closed

[backup] Restore lost some amount of values #13451

pilshchikov opened this issue Jul 27, 2022 · 3 comments
Assignees
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/high High Priority qa_automation Bugs identified via itest-system, LST, Stress automation or causing automation failures

Comments

@pilshchikov
Copy link
Contributor

pilshchikov commented Jul 27, 2022

Jira Link: DB-3065

Description

Case:

  1. Load data - sample-apps workload SqlDataLoad 8 min load, 10 tables. All varchar
  2. At the last minute of load restart the random VM.
  3. Create a backup
  4. Restore on different namespace
  5. Check restored tables with old namespace
  6. Drop old namespace
  7. Repeat from No.1 4 times

Found that one table has different amount of values

> /home/yugabyte/tserver/bin/ysqlsh --c "select count(*) from backup_2460ec_wsqldataload_c11" -h <ip> -d backup_68562e
< count
 12675798
 (1 row) 
> /home/yugabyte/tserver/bin/ysqlsh --c "select count(*) from backup_2460ec_wsqldataload_c11" -h <ip> -d backup_fd2843
< count
 12675711
 (1 row)

Logs:
logs.tar.gz

Version: 2.15.2.0-b40

@pilshchikov pilshchikov added area/docdb YugabyteDB core features status/awaiting-triage Issue awaiting triage labels Jul 27, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Jul 27, 2022
@def-
Copy link
Contributor

def- commented Jul 27, 2022

Is it possible some of the last values are not flushed yet and thus don't get backed up properly? Flushing them manually to check if that fixes it could work to verify if it's a cause.
I had another bug with flushing and missing rows here: #12684

@pilshchikov
Copy link
Contributor Author

@def- no, this one is different. I checked manually several times after an hour from restore and the results are still the same. You can do it by yourself, this universe is still running.

@yugabyte-ci yugabyte-ci added priority/high High Priority and removed priority/medium Medium priority issue status/awaiting-triage Issue awaiting triage labels Jul 27, 2022
@druzac
Copy link
Contributor

druzac commented Aug 2, 2022

@pilshchikov do you have a script that repros this, or can you easily extract one? I'd like to take a look at the sst files in the snapshot, the sst files in the backup, and the sst files in the cluster for the source table to sanity check the theory that the last few writes aren't making it to the backup. I can't confirm that through the logs.

@kripasreenivasan kripasreenivasan added the qa_automation Bugs identified via itest-system, LST, Stress automation or causing automation failures label Sep 13, 2022
@yugabyte-ci yugabyte-ci closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2023
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/high High Priority qa_automation Bugs identified via itest-system, LST, Stress automation or causing automation failures
Projects
None yet
Development

No branches or pull requests

5 participants