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

TiFlash lose metadata after upgrade to v5.4.0 #4434

Closed
KanShiori opened this issue Feb 22, 2022 · 2 comments · Fixed by #4430
Closed

TiFlash lose metadata after upgrade to v5.4.0 #4434

KanShiori opened this issue Feb 22, 2022 · 2 comments · Fixed by #4430

Comments

@KanShiori
Copy link
Collaborator

KanShiori commented Feb 22, 2022

Bug Report

What version of TiDB Operator are you using?

v1.3.0 or v1.3.0-beta.1

What did you do?

If deploying v1.3.0 or v1.3.0-beta.1 operator, TiFlash will lose metadata after upgrading TiFlash to v5.4.0.

What did you expect to see?

What did you see instead?

@KanShiori KanShiori changed the title TiFlash lost data after upgrade to v5.4.0 TiFlash lost metadata after upgrade to v5.4.0 Feb 22, 2022
@KanShiori
Copy link
Collaborator Author

KanShiori commented Feb 22, 2022

For v1.3.0 or v1.3.0-beta.1 operator, operator set the default config storage.raft.dir of TiFlash to a string "/data0/kvstore".

// check "raft.kvstore_path" to be compatible with old version
if common.Get("raft.kvstore_path") == nil {
common.SetIfNil("storage.raft.dir", "/data0/kvstore")
}

This config should be an array so that TiFlash will use the default value "/data0/db/kvstore". So after upgrading to v5.4.0, the value of storage.raft.dir will change, resulting in lost data.

@KanShiori
Copy link
Collaborator Author

Fixed by #4430, and released in v1.3.1

@KanShiori KanShiori changed the title TiFlash lost metadata after upgrade to v5.4.0 TiFlash lose metadata after upgrade to v5.4.0 Feb 22, 2022
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 a pull request may close this issue.

1 participant