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

tikv read only label is lost after tikv restart #6467

Closed
Lily2025 opened this issue May 15, 2023 · 1 comment · Fixed by #6468
Closed

tikv read only label is lost after tikv restart #6467

Lily2025 opened this issue May 15, 2023 · 1 comment · Fixed by #6468

Comments

@Lily2025
Copy link

Bug Report

What did you do?

rolling restart tikv

What did you expect to see?

tikv read only label is not lost

What did you see instead?

tikv read only label is lost after tikv restart
image

What version of PD are you using (pd-server -V)?

/ # ./pd-server -V
Release Version: v6.5.1
Edition: Community
Git Commit Hash: bd80719
Git Branch: heads/refs/tags/v6.5.1
UTC Build Time: 2023-03-09 10:57:50

@Lily2025 Lily2025 added the type/bug The issue is confirmed as a bug. label May 15, 2023
@Lily2025
Copy link
Author

/type bug
/severity critical

ti-chi-bot bot pushed a commit that referenced this issue May 15, 2023
…6470)

ref #5510, close #6467, ref #6468

#5510 introduced a bug that would cause the store labels to be overwritten wrongly after the store reboot.
This PR fixed this issue.

Signed-off-by: JmPotato <ghzpotato@gmail.com>

Co-authored-by: JmPotato <ghzpotato@gmail.com>
ti-chi-bot bot pushed a commit that referenced this issue May 15, 2023
…6469)

ref #5510, close #6467, ref #6468

#5510 introduced a bug that would cause the store labels to be overwritten wrongly after the store reboot.
This PR fixed this issue.

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: JmPotato <ghzpotato@gmail.com>

Co-authored-by: JmPotato <ghzpotato@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants