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.

Sign up for GitHub

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

Jump to bottom

sql: restoring 2.1 backup into 20.1 cluster succeeds but seems to be in a bad state #44453

Closed
yuzefovich opened this issue Jan 28, 2020 · 0 comments · Fixed by #47234
Closed

sql: restoring 2.1 backup into 20.1 cluster succeeds but seems to be in a bad state #44453

yuzefovich opened this issue Jan 28, 2020 · 0 comments · Fixed by #47234
Assignees
@pbardea
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
Disaster Recovery Sprint Status

Comments

@yuzefovich
Copy link
Member

yuzefovich commented Jan 28, 2020 •
edited
Loading

I successfully restored a backup of a database (that I believe was created on 2.1 cluster) onto the current master (20.1). However, the system tables seem to be in a bad state.

The backup is linked to our internal wiki page about querylog workload (https://cockroachlabs.atlassian.net/wiki/spaces/ENG/pages/74777114/Testing+with+querylog+workload)

Once the data restored, running SELECT column_name, data_type FROM [SHOW COLUMNS FROM <table_name>]; (for one of the newly-restored tables) crashes the cluster.

My guess is that using this particular backup might not be necessary - maybe creating any backup on 2.1 cluster and then restoring it into 20.1 will have a similar behavior, but I didn't check this.

Assigning to @dt for triage.
@yuzefovich yuzefovich added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Jan 28, 2020
@yuzefovich yuzefovich added this to Triage in Disaster Recovery Backlog via automation Jan 28, 2020
@dt dt assigned pbardea and unassigned dt Jan 28, 2020
@dt dt moved this from Triage to Bug in Disaster Recovery Backlog Mar 6, 2020
@pbardea pbardea added this to Next Sprint (May) in Disaster Recovery Sprint Status via automation Apr 8, 2020
@pbardea pbardea moved this from Next Sprint (May) to In progress in Disaster Recovery Sprint Status Apr 8, 2020
This was referenced Apr 8, 2020
Merged
Closed
Merged
@craig craig bot closed this as completed in 0222b51 Apr 9, 2020
Disaster Recovery Backlog automation moved this from Bug to Closed Apr 9, 2020
Disaster Recovery Sprint Status automation moved this from In progress to Done Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pbardea pbardea

Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
No open projects
Disaster Recovery Sprint Status
  
Closed
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

sql: populate Oid on type upgrade pbardea/cockroach
3 participants
@dt @pbardea @yuzefovich