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

Consider applied index in unsafe recovery #7919

Closed
glorv opened this issue Mar 14, 2024 · 0 comments · Fixed by #7920
Closed

Consider applied index in unsafe recovery #7919

glorv opened this issue Mar 14, 2024 · 0 comments · Fixed by #7920
Labels
type/development The issue belongs to a development tasks

Comments

@glorv
Copy link
Contributor

glorv commented Mar 14, 2024

Development Task

After tikv/tikv#16626, It is possible applied_index > last_index, so we should selection peer with maximum applied index to recovery more data.
@glorv glorv added the type/development The issue belongs to a development tasks label Mar 14, 2024
@glorv glorv mentioned this issue Mar 14, 2024
Merged
@ti-chi-bot ti-chi-bot bot closed this as completed in #7920 Apr 7, 2024
ti-chi-bot bot added a commit that referenced this issue Apr 7, 2024
@glorv @ti-chi-bot @Connor1996
unsafe_recovery: also consider applied index when selects force leader (
569f3e0 
#7920)

close #7919, ref tikv/tikv#16717

Signed-off-by: glorv <glorvs@163.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Co-authored-by: Connor <zbk602423539@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/development The issue belongs to a development tasks
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

unsafe_recovery: also consider applied index when selects force leader glorv/pd
1 participant
@glorv