-
Notifications
You must be signed in to change notification settings - Fork 725
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
Unsafe recovery auto detect mode doesn't work #5753
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
Connor1996
added a commit
to Connor1996/pd
that referenced
this issue
Dec 5, 2022
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
nolouch
added
affects-6.1
This bug affects the 6.1.x(LTS) versions.
and removed
may-affects-6.2
may-affects-6.3
may-affects-6.4
may-affects-6.5
labels
Dec 5, 2022
ti-chi-bot
added a commit
that referenced
this issue
Dec 5, 2022
close #5753 Fix unsafe recovery auto-detect mode by passing detected failed stores to TiKV Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Dec 5, 2022
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
ti-chi-bot
added a commit
that referenced
this issue
Dec 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
What did you do?
Run unsafe recovery auto-detect mode after performing pd recover
What did you expect to see?
Finish successfully
What did you see instead?
get stuck in enter force leader stage and finally timeout.
In TiKV log, it prints
Unsafe recovery, reject pre force leader due to has quorum
What version of PD are you using (
pd-server -V
)?v6.4.0
The text was updated successfully, but these errors were encountered: