pingcap / pingcap/tidb

Full backup may slowdown during leader eviction

Open
#65,410 0 comments 0 reactions 0 assignees View on GitHub
affects-8.5 component/br severity/major type/bug
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
After we implement store level backup in v8.5.

When backup starts during leader eviction, a store backup may incorrectly consider itself finished and return early.

The backup will only restart in the next round. If a single round takes a long time, this behavior significantly extends the backup retention window and can effectively double the total backup time.
Image

![Image](https://github.com/user-attachments/assets/1aa754e8-2b02-4537-826f-02d0e7f4e376)

### 2. What did you expect to see? (Required)
All stores participate in the backup process and continue backing up data as expected during the backup round.
### 3. What did you see instead (Required)
Some stores did not perform any backup work during this round and returned early, even though the backup was still in progress.
### 4. What is your TiDB version? (Required)
v8.5

Contributor guide

Open the contributing guide

Research direction

The issue names no source files, tests, or entry points. Start by locating the v8.5 store-level backup and leader-eviction paths, then trace their interaction during a backup round. Done means every store continues participating during leader eviction instead of returning early.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.